Eduardo, creio que o problema decorre do jogo de caracteres usado...
No meu caso, uma vez que vivo em Portugal, uso o jogo LATIN9 quando crio uma
nova base de dados.
Simplificando:
CREATE DATABASE xpto
WITH OWNER = postgres
ENCODING = 'LATIN9'
TABLESPACE = pg_default;
Hélder M.
Juliann Meyer <[EMAIL PROTECTED]> writes:
> I don't know if this is the correct list, but does any
> one know what sqlstate code YE000 indicates?
A quick look in the source code finds
#define ECPG_SQLSTATE_ECPG_INTERNAL_ERROR "YE000"
Probably a complete bug report is indicated.
I don't know if this is the correct list, but does any
one know what sqlstate code YE000 indicates?
I checked the Appendix of sqlstate codes for the
version 7.4.8 that is being used and I don't see it
on the list?
All I can tell is it has something to do with the cursor
that is trying to be opene
Pessoal estou com um problema para usar a função Upper, pelo que parece esta havendo uma incompatibilidade pois qd rodo o sql no linux ((Gentoo) funciona legal, agora no windows não ta trazendo os resultados. Em ambos os casos estou usando o Postgresql
8.1 com PgAdmin 1.4.1, o sql é o seguinte.sel
On Tue, 20 Jun 2006, Dirk Jagdmann wrote:
Column id should be indexed indeed. Anyway, I'm not sure about any
performance improvement using that last method, as the most consuming
operation might be the DELETE operation, not really the SELECT operation,
when dealing with a huge volume of data.
Column id should be indexed indeed. Anyway, I'm not sure about any performance
improvement using that last method, as the most consuming operation might be
the DELETE operation, not really the SELECT operation, when dealing with a huge
volume of data.
why worry, there are a maximum of 30 Ent
