On Thursday, January 16, 2003, at 10:02 AM, REMICOURT Beno�t wrote:
Rhett, can you send me the link of this driver ? I found some driver butThe one I used that worked was the JDBC2 driver from http://jdbc.postgresql.org/download.html, build 107 (Jan 14 2003).
same problem for me and when getting string it cuts any string at the first
� | � | � ...
I have not tried accented characters. The described problem potentially could be caused by the driver (or postgresql) having been compiled with incompatible character sets, but I don't know enough about postgresql to say for certain. (I recall that postgresql used to have to be configured to use unicode explicitly at compile time, but I don't know if that is still the case.)
Also:
I am experiencing this bug since december 2002, the problem is that afterI don't think this is the same bug. This sounds like a JDO caching problem. If you could come up with a reproducible test case, Bruce Synder could probably help you out.
several tests the cache of castor has been purged... and now, i cannot
update any old objects because it seems to try to compare my object with the
one in cache which don't exists and with timestamp value = 0.
After that, I try to skeep timestamp matching... :(
And castor says that my object was modified since it was
loaded/created/updated... and don't release the readlock on my object. The
result is that i can't update any more objects of the same type since the
lock is not released by the database.
Rhett
On Thursday, January 16, 2003, at 10:02 AM, REMICOURT Beno�t wrote:
Hi,----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
I am experiencing this bug since december 2002, the problem is that after
several tests the cache of castor has been purged... and now, i cannot
update any old objects because it seems to try to compare my object with the
one in cache which don't exists and with timestamp value = 0.
After that, I try to skeep timestamp matching... :(
And castor says that my object was modified since it was
loaded/created/updated... and don't release the readlock on my object. The
result is that i can't update any more objects of the same type since the
lock is not released by the database.
Rhett, can you send me the link of this driver ? I found some driver but
same problem for me and when getting string it cuts any string at the first
� | � | � ...
The one i get is from castor dev and works fine with accents.
Is anyone else experience probleme using castor with postgres ? For my part,
I use castor with informix, db2, sqlserver, mysql, oracle but I only have
problems with postgresql ;(
Beno�t
-----Message d'origine-----
De : Rhett Sutphin [mailto:[EMAIL PROTECTED]]
Envoy� : mardi 14 janvier 2003 22:58
� : [EMAIL PROTECTED]
Objet : Re: [castor-dev] PosstgreSQL 7.3 JDBC timestamp bug
Hi again,
I'm replying to myself to let you all know that this bug is fixed now.
The newest 7.3 JDBC drivers from jdbc.postgresql.org contain the patch.
Rhett
On Friday, January 10, 2003, at 04:09 PM, Rhett Sutphin wrote:
Hi,-----------------------------------------------------------
I've discovered a fairly minor bug in the JDBC driver that ships with
PostgreSQL 7.3. It causes a bogus ObjectModifiedException in test
TC20 (TypeHandling) of the JDO test suite, so it is possible that it
could impact some castor users. That's why I'm mentioning it here.
The message I sent to the pgsql-jdbc list hasn't made it into their
archive yet, so here's a summary of the bug: when you retrieve a
TIMESTAMP field from a PostgreSQL 7.3 database and it contains
fractional second information, the fractional second information will
be wrong if there is more than one decimal-place's worth. The problem
this caused with the JDO tests was that the cached version of an
affected timestamp field was always out-of-sync with the actual
database, leading to the aforementioned ObjectModifiedException.
Anyway, all the details are in my pgsql-jdbc post, so if you are
interested, wait for a while and it should show up here:
http://archives.postgresql.org/pgsql-jdbc/2003-01/index.php. Or if
you are in a hurry, you can e-mail me and I'll forward you the > message.
Rhett
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
Tout usage de ce message par une personne autre que son destinataire est
strictement interdit. L'int�grit� de ce message n'�tant pas assur�e sur
Internet, Le Groupe EUROGICIEL ne peut �tre tenu responsable de son contenu.
Toute utilisation ou diffusion non autoris�e est interdite. Si vous n'�tes
pas destinataire de ce message, merci de le d�truire et d'avertir
l'exp�diteur.
The information above is for the sole use of the individual or entity to
which it is intended. If you are not the intended recipient of this message,
you are hereby notified that any dissemination, distribution or copying of
this document is strictly prohibited. The integrity of this message cannot
be guaranteed on the Internet. EUROGICIEL Group shall in no way be liable
for its content. Please destroy this message and notify the sender.
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
