Hi Gnari,
I'll do some more test tonight to figure out if it's a tomcat problem
and I'll get back to you with this info.
Thanks!
/David
maybe some difference in the environments that the two
tomcats run in? are their locales the same ?
gnari
---(end of
Hi,
I really have a problem with a production environment (RH 9, Postgresql
7.4).
When executing a stored procedure on my computer (development
environment: 7.4 under cygwin. ) everything is oki
When I deploy on the production env the same stored procedure with the
same data (different OS and
On Mon, 2005-03-14 at 16:32 -0500, David Gagnon wrote:
Hi,
I really have a problem with a production environment (RH 9, Postgresql
7.4).
When I deploy on the production env the same stored procedure with the
same data (different OS and postgresql instance) the stored procedure
crash. I
Thanks for your answer.
The ISP created the db fom me .. So I don't have this information. I
search the web to know how to get this info via PgadminIII and I haven't
found :-( Is there a way to get this information once the database have
been created ? I looked via psql .. I haven`t found
David Gagnon wrote:
Thanks for your answer.
The ISP created the db fom me .. So I don't have this information. I
search the web to know how to get this info via PgadminIII and I
haven't found :-( Is there a way to get this information once the
database have been created ? I looked via psql
Hi
Thanks for the tips. Locale are the same ... unless I don`t look at
the right thing...
Production ENV
-
lc_collate | C
lc_ctype | C
lc_messages| C
lc_monetary| C
lc_numeric
David Gagnon wrote:
Hi
Thanks for the tips. Locale are the same ... unless I don`t look at
the right thing...
...
Can you try to run the procedure from some other environment? It seems
you use some Java class, so I mean try psql, phpPgAdmin or something
different.
Miroslav
begin:vcard
I did tried to update the stored-procedure via PgadminIII and it
worked. The problem seems to be JDBC driver .. But all works well on my
TOMCA/POSTGRESL/WINDOWS platform.
I think it's something in the database setting .. is there other setting
that can cause this behavior ?
Thanks!
/David
On Mon, 2005-03-14 at 19:13 -0500, David Gagnon wrote:
I did tried to update the stored-procedure via PgadminIII and it
worked. The problem seems to be JDBC driver .. But all works well on my
TOMCA/POSTGRESL/WINDOWS platform.
I think it's something in the database setting .. is there
