Fórum Biometria No Firebird #407691
15/09/2011
0
Olá Amigos estou com uma dúvida .. preciso armazenar uma biometria que virá de um relógio de ponto.. gostaria de saber .. que tipo de campo seria o mais adequado ..desde já agradeço..
Eduardo
Curtir tópico
+ 0
Responder
Posts
20/09/2011
Joni Nunes
Bom dia, temos um sistema com essa mesma idéia, porém usamos Oracle, logo usamos BLOB, o Firebird também da suporte a esse tipo de dados, segue detalhes:
Level of support:
Full support for:
= (assignment);
=, , = and synonyms (comparison);
|| (concatenation);
BETWEEN, IS [NOT] DISTINCT FROM, IN, ANY|SOME and ALL.
Partial support for STARTING [WITH], LIKE and CONTAINING: an error is raised if the second argument is 32 KB or longer.
SELECT DISTINCT, ORDER BY and GROUP BY work on the BLOB ID, not the contents. This makes them as good as useless, except that SELECT DISTINCT weeds out multiple NULLs, if present. GROUP BY behaves oddly in that it groups together equal rows if they are adjacent, but not if they are apart.
Any issues with BLOBs in internal functions and aggregate functions are discussed in their respective sections.
Abraço
Level of support:
Full support for:
= (assignment);
=, , = and synonyms (comparison);
|| (concatenation);
BETWEEN, IS [NOT] DISTINCT FROM, IN, ANY|SOME and ALL.
Partial support for STARTING [WITH], LIKE and CONTAINING: an error is raised if the second argument is 32 KB or longer.
SELECT DISTINCT, ORDER BY and GROUP BY work on the BLOB ID, not the contents. This makes them as good as useless, except that SELECT DISTINCT weeds out multiple NULLs, if present. GROUP BY behaves oddly in that it groups together equal rows if they are adjacent, but not if they are apart.
Any issues with BLOBs in internal functions and aggregate functions are discussed in their respective sections.
Abraço
Responder
Gostei + 0
Clique aqui para fazer login e interagir na Comunidade :)