Skip site navigation (1) Skip section navigation (2)

Re: JDBC patch (attempt#2) for util.Serialize and jdbc2.PreparedStatement

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: "Robert B(dot) Easter" <reaster(at)comptechnews(dot)com>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: JDBC patch (attempt#2) for util.Serialize and jdbc2.PreparedStatement
Date: 2001-08-26 00:53:24
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugspgsql-patches
Both diffs applied.  Test files not installed.  Thanks.

> (attempt #2) Don't use serializepatch.tgz that I sent before, use the file 
> attached now to this email instead.
> The attached file: SerializePatch2.tgz, contains a patch for 
> org.postgresql.util.Serialize and org.postgresql.jdbc2.PreparedStatement that 
> fixes the ability to "serialize" a simple java class into a postgres table. 
> The current cvs seems completely broken in this support, so the patch puts it 
> into working condition, granted that there are many limitations with 
> serializing java classes into Postgres.
> A little test program is included with the patches. ?The comments in the 
> Serialize class tries to explain how all this works.
> Note:
> The code to do serialize appears to have been in the driver since Postgres 
> 6.4, according to some comments in the source.  My code is not adding any 
> totally new ability to the driver, rather just fixing what is there so that 
> it actually is usable.  I do not think that it should affect any existing 
> functions of the driver that people regularly depend on.
> The code is activated if you use jdbc2.PreparedStatement and try to setObject 
> some java class type that is unrecognized, like not String or not some other 
> primitive type.  This will cause a sequence of function calls that results in 
> an instance of Serialize being instantiated for the class type passed.  The 
> Serialize constructor will query pg_class to see if it can find an existing 
> table that matches the name of the java class. If found, it will continue and 
> try to use the table to store the object, otherwise an SQL exception is 
> thrown and no harm is done.  Serialize.create() has to be used to setup the 
> table for a java class before anything can really happen with this code other 
> than an SQLException (unless by some freak chance a table exists that it 
> thinks it can use).
> I saw a difference in between 7.1.3 and 7.2devel that I didn't 
> notice before, so I had to redo my changes from the 7.2devel version (why I 
> had to resend this patch now).  I was missing the fixString stuff, which is 
> nice and is imporant to ensure the inserts will not fail due to embedded 
> single quote or unescaped backslashes. I changed that fixString function in 
> Serialize just a little since there is no need to muddle with escaping 
> newlines: only escaping single quote and literal backslashes is needed. 
> Postgres appears to insert newlines within strings without trouble.

[ Attachment, skipping... ]

> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly

  Bruce Momjian                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to

pgsql-bugs by date

Next:From: Bruce MomjianDate: 2001-08-26 01:06:25
Subject: Re: Bug #428: Another security issue with the JDBC driver.
Previous:From: Bruce MomjianDate: 2001-08-26 00:19:20
Subject: Re: Bug #424: JDBC driver security issue.

pgsql-patches by date

Next:From: Bruce MomjianDate: 2001-08-26 00:55:30
Subject: Re: resultmap for OpenUNIX 8
Previous:From: Larry RosenmanDate: 2001-08-26 00:18:55
Subject: Re: [PATCHES] Makefile.PL for

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group