pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedJDBC Problem
17+ messages / 12 participants
[nested] [flat]
* JDBC Problem
@ 2000-04-04 09:07 Michael Yeung <michaely@alphanet.net.au>
0 siblings, 0 replies; 17+ messages in thread
From: Michael Yeung @ 2000-04-04 09:07 UTC (permalink / raw)
To: pgsql-interfaces
Hi all,
I have installed the jdbc-6.5.1.2.jar. However, when i try to run a program, which connects to the remote postgresql , it tells me that :
java.sql.SQLException : Unsupported frontend protocol
Any Suggestions will be highly appreciated !!
MIC
^ permalink raw reply [nested|flat] 17+ messages in thread
* JDBC problem
@ 2000-08-22 11:46 BogdanKRomski <b.kromski@gaschka.pl>
0 siblings, 1 reply; 17+ messages in thread
From: BogdanKRomski @ 2000-08-22 11:46 UTC (permalink / raw)
To: pgsql-interfaces
Hello
I'm using the Postgresql 6.5 and i try to perform statement
INSERT into KEY_ITEM (key_item_id,keyName) values(((SELECT
MAX(key_item_id) FROM KEY_ITEM)+1),?)
and I get the message :
Error: ERROR: parser: parse error at or near "select"
I'm not sure but part "(SELECT MAX(key_item_id) FROM KEY_ITEM)+1)" of
statement does't work
thanks for all informations
Bogdan Kromski
ps. on Oracle and Sybase it is working correct
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: JDBC problem
@ 2000-08-24 23:15 John McKown <jmckown@prodigy.net>
parent: BogdanKRomski <b.kromski@gaschka.pl>
0 siblings, 1 reply; 17+ messages in thread
From: John McKown @ 2000-08-24 23:15 UTC (permalink / raw)
To: BogdanKRomski <b.kromski@gaschka.pl>; +Cc: pgsql-interfaces
The syntax that I've seen is:
insert into KEY_ITEM (key_item_id,keyname) values
(select max(key_item_id)+1,'?' FROM KEY_ITEM);
Just out of curiousity, why not make key_item_id a SERIAL field? That way,
if you don't specify a value, it gets the next value from the associated
sequence.
On Tue, 22 Aug 2000, BogdanKRomski wrote:
> Hello
>
> I'm using the Postgresql 6.5 and i try to perform statement
>
> INSERT into KEY_ITEM (key_item_id,keyName) values(((SELECT
> MAX(key_item_id) FROM KEY_ITEM)+1),?)
>
> and I get the message :
>
> Error: ERROR: parser: parse error at or near "select"
>
> I'm not sure but part "(SELECT MAX(key_item_id) FROM KEY_ITEM)+1)" of
> statement does't work
>
> thanks for all informations
>
> Bogdan Kromski
>
> ps. on Oracle and Sybase it is working correct
>
^ permalink raw reply [nested|flat] 17+ messages in thread
* RE: JDBC problem
@ 2000-08-25 06:31 Peter Mount <petermount@it.maidstone.gov.uk>
0 siblings, 0 replies; 17+ messages in thread
From: Peter Mount @ 2000-08-25 06:31 UTC (permalink / raw)
To: 'BogdanKRomski' <b.kromski@gaschka.pl>; pgsql-interfaces
The parser error is from the backend not JDBC (as it doesnt parse anything
other than PreparedStatement's).
I think it's the sub-select that's causing the problem, as it's not
supported in 6.5.
Peter
--
Peter Mount
Enterprise Support Officer, Maidstone Borough Council
Email: petermount@it.maidstone.gov.uk
WWW: http://www.maidstone.gov.uk
All views expressed within this email are not the views of Maidstone Borough
Council
-----Original Message-----
From: BogdanKRomski [mailto:b.kromski@gaschka.pl]
Sent: Tuesday, August 22, 2000 12:47 PM
To: pgsql-interfaces@postgresql.org
Subject: [INTERFACES] JDBC problem
Hello
I'm using the Postgresql 6.5 and i try to perform statement
INSERT into KEY_ITEM (key_item_id,keyName) values(((SELECT
MAX(key_item_id) FROM KEY_ITEM)+1),?)
and I get the message :
Error: ERROR: parser: parse error at or near "select"
I'm not sure but part "(SELECT MAX(key_item_id) FROM KEY_ITEM)+1)" of
statement does't work
thanks for all informations
Bogdan Kromski
ps. on Oracle and Sybase it is working correct
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: JDBC problem
@ 2000-08-25 08:49 Cedar Cox <cedarc@visionforisrael.com>
parent: John McKown <jmckown@prodigy.net>
0 siblings, 2 replies; 17+ messages in thread
From: Cedar Cox @ 2000-08-25 08:49 UTC (permalink / raw)
To: John McKown <jmckown@prodigy.net>; +Cc: BogdanKRomski <b.kromski@gaschka.pl>; pgsql-interfaces
On Thu, 24 Aug 2000, John McKown wrote:
> The syntax that I've seen is:
>
> insert into KEY_ITEM (key_item_id,keyname) values
> (select max(key_item_id)+1,'?' FROM KEY_ITEM);
>
> Just out of curiousity, why not make key_item_id a SERIAL field? That way,
> if you don't specify a value, it gets the next value from the associated
> sequence.
I was going to ask you to explain SERIAL but the documentation makes it
fairly clear.. basically just the next value, yes? Simply setting the
field type to SERIAL seems to be the same as the MS Access 'autonumber'
field. Is this correct?
One detail that seems to have an advantage over the MAX+1 method is that
in the case of adding a new record, deleting it, then adding another new
record the ID will not be reused (correct?).
Question: What happens when transactions enter the picture? Will you get
duplicate values, or holes, or does it work just fine?
-Cedar
^ permalink raw reply [nested|flat] 17+ messages in thread
* RE: JDBC problem
@ 2000-08-25 11:21 Peter Mount <PeterM@maidstone.gov.uk>
0 siblings, 0 replies; 17+ messages in thread
From: Peter Mount @ 2000-08-25 11:21 UTC (permalink / raw)
To: 'Cedar Cox' <cedarc@visionforisrael.com>; John McKown <jmckown@prodigy.net>; +Cc: BogdanKRomski <b.kromski@gaschka.pl>; pgsql-interfaces
Serial actually allocates numbers in blocks (default=1), so you won't get a
duplicate.
The plus side of this is that you can set the block size >1, so if you are
loading lots of data, you can set it to 10, then it only allocates a new
block once the last one is used up. However, if your connection is closed
before the block is used, the unused numbers are lost.
Peter
PS: Major email problems here at mbc, so I may not be able to reply to any
directly written replies for a while (I accidentally erased all the
addresses, whoops)...
--
Peter Mount
Enterprise Support Officer, Maidstone Borough Council
Email: petermount@it.maidstone.gov.uk
WWW: http://www.maidstone.gov.uk
All views expressed within this email are not the views of Maidstone Borough
Council
-----Original Message-----
From: Cedar Cox [mailto:cedarc@visionforisrael.com]
Sent: Friday, August 25, 2000 9:50 AM
To: John McKown
Cc: BogdanKRomski; pgsql-interfaces@postgresql.org
Subject: Re: [INTERFACES] JDBC problem
On Thu, 24 Aug 2000, John McKown wrote:
> The syntax that I've seen is:
>
> insert into KEY_ITEM (key_item_id,keyname) values
> (select max(key_item_id)+1,'?' FROM KEY_ITEM);
>
> Just out of curiousity, why not make key_item_id a SERIAL field? That way,
> if you don't specify a value, it gets the next value from the associated
> sequence.
I was going to ask you to explain SERIAL but the documentation makes it
fairly clear.. basically just the next value, yes? Simply setting the
field type to SERIAL seems to be the same as the MS Access 'autonumber'
field. Is this correct?
One detail that seems to have an advantage over the MAX+1 method is that
in the case of adding a new record, deleting it, then adding another new
record the ID will not be reused (correct?).
Question: What happens when transactions enter the picture? Will you get
duplicate values, or holes, or does it work just fine?
-Cedar
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: JDBC problem
@ 2000-08-25 14:35 Ross J. Reedstrom <reedstrm@rice.edu>
parent: Cedar Cox <cedarc@visionforisrael.com>
1 sibling, 0 replies; 17+ messages in thread
From: Ross J. Reedstrom @ 2000-08-25 14:35 UTC (permalink / raw)
To: pgsql-interfaces
On Fri, Aug 25, 2000 at 11:49:32AM +0300, Cedar Cox wrote:
>
>
> One detail that seems to have an advantage over the MAX+1 method is that
> in the case of adding a new record, deleting it, then adding another new
> record the ID will not be reused (correct?).
>
> Question: What happens when transactions enter the picture? Will you get
> duplicate values, or holes, or does it work just fine?
Well, in my opinion it works just fine, but that does mean you get holes.
This has been discussed do death over on GENERAL a number of times. In
order to avoid locking on the serial seequence generator, multiple
transacations each get to increment the counter, but do not roll it
back on transaction failure. And each connection maintains it's own
state of the underlying sequence, so that currval('table_field_seq')
is multiuser safe.
And as you mention above, not reusing numbers also leads to holes, so
your app needs to be able to handle that, anyway.
Ross
--
Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu>
NSBRI Research Scientist/Programmer
Computer and Information Technology Institute
Rice University, 6100 S. Main St., Houston, TX 77005
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: JDBC problem
@ 2000-08-25 17:43 John McKown <jmckown@prodigy.net>
parent: Cedar Cox <cedarc@visionforisrael.com>
1 sibling, 1 reply; 17+ messages in thread
From: John McKown @ 2000-08-25 17:43 UTC (permalink / raw)
To: Cedar Cox <cedarc@visionforisrael.com>; +Cc: BogdanKRomski <b.kromski@gaschka.pl>; pgsql-interfaces
On Fri, 25 Aug 2000, Cedar Cox wrote:
>
>
> On Thu, 24 Aug 2000, John McKown wrote:
>
> > The syntax that I've seen is:
> >
> > insert into KEY_ITEM (key_item_id,keyname) values
> > (select max(key_item_id)+1,'?' FROM KEY_ITEM);
> >
> > Just out of curiousity, why not make key_item_id a SERIAL field? That way,
> > if you don't specify a value, it gets the next value from the associated
> > sequence.
>
> I was going to ask you to explain SERIAL but the documentation makes it
> fairly clear.. basically just the next value, yes? Simply setting the
> field type to SERIAL seems to be the same as the MS Access 'autonumber'
> field. Is this correct?
I'm not familiar with MS Access, but I'll bet that it is very similiar to
'autonumber'. However, a sequence can be shared by multple tables /
fields. This means that a single table/field could have "holes" in the
sequence number.
>
> One detail that seems to have an advantage over the MAX+1 method is that
> in the case of adding a new record, deleting it, then adding another new
> record the ID will not be reused (correct?).
Correct. The sequence is independant of the table and the value only
increases.
>
> Question: What happens when transactions enter the picture? Will you get
> duplicate values, or holes, or does it work just fine?
A good question to which I don't know the answer.
However, after thinking about it a bit, I would guess that the sequence is
"locked" for the duration of the transaction. This would imply that all
other transactions which needed to access the sequence would be stalled
until this transaction ended. When the transaction ended, then sequence
would either have the highest number assigned so far, or would be rolled
back to the same value it had when the transaction started.
The above is just my guess. If the sequence is not "locked", then I would
guess that an aborted transaction would cause the sequence to end up with
holes. Actually, multiple tables and fields can share a sequence (why
would anybody do this?). This means that a single table could have
"holes" in the sequence.
Under no circumstances would I expect duplicates.
>
> -Cedar
>
>
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: JDBC problem
@ 2000-08-27 06:04 Cedar Cox <cedarc@visionforisrael.com>
parent: John McKown <jmckown@prodigy.net>
0 siblings, 1 reply; 17+ messages in thread
From: Cedar Cox @ 2000-08-27 06:04 UTC (permalink / raw)
To: John McKown <jmckown@prodigy.net>; +Cc: BogdanKRomski <b.kromski@gaschka.pl>; pgsql-interfaces
On Fri, 25 Aug 2000, John McKown wrote:
[talking about sequences]
> > Question: What happens when transactions enter the picture? Will you get
> > duplicate values, or holes, or does it work just fine?
>
> A good question to which I don't know the answer.
>
> However, after thinking about it a bit, I would guess that the sequence is
> "locked" for the duration of the transaction. This would imply that all
> other transactions which needed to access the sequence would be stalled
> until this transaction ended. When the transaction ended, then sequence
> would either have the highest number assigned so far, or would be rolled
> back to the same value it had when the transaction started.
>
> The above is just my guess. If the sequence is not "locked", then I would
> guess that an aborted transaction would cause the sequence to end up with
> holes. Actually, multiple tables and fields can share a sequence (why
> would anybody do this?).
I'm not sure either, but I'm sure it could be used for something
interesting..
> This means that a single table could have "holes" in the sequence.
>
> Under no circumstances would I expect duplicates.
This 'locking' thing was what I was wondering about. If 'sequence
locking' does actually take place, I don't like the idea of other
transactions having to wait but it seems necessary. On the other hand,
holes in a sequence shouldn't be an issue for us so 'no locking' would be
just fine. Can someone confirm? I just want to make sure I have a
correct understanding of how it works..
Thanks
-Cedar
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: JDBC problem
@ 2000-08-27 18:36 Joachim Achtzehnter <joachim@kraut.bc.ca>
parent: Cedar Cox <cedarc@visionforisrael.com>
0 siblings, 1 reply; 17+ messages in thread
From: Joachim Achtzehnter @ 2000-08-27 18:36 UTC (permalink / raw)
To: Cedar Cox <cedarc@visionforisrael.com>; +Cc: John McKown <jmckown@prodigy.net>; BogdanKRomski <b.kromski@gaschka.pl>; pgsql-interfaces
Today, in a message to John McKown, Cedar Cox wrote:
>
> On Fri, 25 Aug 2000, John McKown wrote:
> >
> > However, after thinking about it a bit, I would guess that the sequence is
> > "locked" for the duration of the transaction. This would imply that all
> > other transactions which needed to access the sequence would be stalled
> > until this transaction ended.
No, the sequence does not remain locked for the duration of the
transaction. If that was the case sequences would be nearly useless for
most applications.
> > The above is just my guess.
It is always dangerous to guess with these things. :-)
> This 'locking' thing was what I was wondering about. If 'sequence
> locking' does actually take place,
It doesn't.
> On the other hand, holes in a sequence shouldn't be an issue for us so
> 'no locking' would be just fine.
The purpose of these sequences is to generate unique keys, therefore,
holes don't matter.
Joachim
--
work: joachima@realtimeint.com (http://www.realtimeint.com)
private: joachim@kraut.bc.ca (http://www.kraut.bc.ca)
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: JDBC problem
@ 2000-08-28 05:52 Cedar Cox <cedarc@visionforisrael.com>
parent: Joachim Achtzehnter <joachim@kraut.bc.ca>
0 siblings, 0 replies; 17+ messages in thread
From: Cedar Cox @ 2000-08-28 05:52 UTC (permalink / raw)
To: Joachim Achtzehnter <joachim@kraut.bc.ca>; +Cc: John McKown <jmckown@prodigy.net>; BogdanKRomski <b.kromski@gaschka.pl>; pgsql-interfaces
On Sun, 27 Aug 2000, Joachim Achtzehnter wrote:
> > On the other hand, holes in a sequence shouldn't be an issue for us so
> > 'no locking' would be just fine.
>
> The purpose of these sequences is to generate unique keys, therefore,
> holes don't matter.
Exactly. Thanks for the input..
-Cedar
^ permalink raw reply [nested|flat] 17+ messages in thread
* JDBC Problem
@ 2000-11-16 14:54 tony <tony@uickarate.com>
0 siblings, 1 reply; 17+ messages in thread
From: tony @ 2000-11-16 14:54 UTC (permalink / raw)
To: pgsql-interfaces
I have a problem with loading the JDBC Driver.
So far, my java code does nothing but to load the driver, and
it gives SQLException with message "No suitable driver".
I made the postgresql.jar with
>make jdbc2
(because I am using jdk1.3)
and I used
>jar tf postgresql.jar
to make sure that the driver was included.
(postgresql/Driver.class)
My CLASSPATH is following:
:/usr/local/lib/postgresql.jar:/usr/local/jdk1.3/bin/:/home/tony/classes/
I am trying to load the driver by doing
>Class.forName("postgresql.Driver");
This is under linux platform. Please let me know what could be
wrong if you see anything wrong.
Thanks!
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: JDBC Problem
@ 2000-11-16 15:23 tony <tony@uickarate.com>
parent: Michael Stephenson <mstephenson@tirin.openworld.co.uk>
0 siblings, 0 replies; 17+ messages in thread
From: tony @ 2000-11-16 15:23 UTC (permalink / raw)
To: pgsql-interfaces
Michael, Peter, Chris,
Thanks for the advice. I forgot to mention that
I tried org.postgresql.Driver and it didn't work...
Tony
----- Original Message -----
From: "Michael Stephenson" <mstephenson@tirin.openworld.co.uk>
To: "tony" <tony@uickarate.com>
Cc: "pgsql-interfaces" <pgsql-interfaces@postgresql.org>
Sent: Thursday, November 16, 2000 11:12 AM
Subject: Re: [INTERFACES] JDBC Problem
> > I am trying to load the driver by doing
> > >Class.forName("postgresql.Driver");
>
> Try:
>
> Class.forName("org.postgresql.Driver");
>
> Hope this helps
>
> Michael Stephenson
>
>
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: JDBC Problem
@ 2000-11-16 16:12 Michael Stephenson <mstephenson@tirin.openworld.co.uk>
parent: tony <tony@uickarate.com>
0 siblings, 1 reply; 17+ messages in thread
From: Michael Stephenson @ 2000-11-16 16:12 UTC (permalink / raw)
To: tony <tony@uickarate.com>; +Cc: pgsql-interfaces
> I am trying to load the driver by doing
> >Class.forName("postgresql.Driver");
Try:
Class.forName("org.postgresql.Driver");
Hope this helps
Michael Stephenson
^ permalink raw reply [nested|flat] 17+ messages in thread
* RE: JDBC Problem
@ 2000-11-16 16:14 Peter Mount <petermount@maidstone.gov.uk>
0 siblings, 0 replies; 17+ messages in thread
From: Peter Mount @ 2000-11-16 16:14 UTC (permalink / raw)
To: 'tony' <tony@uickarate.com>; pgsql-interfaces
What version of the driver are you using?
Versions 6.5.x and earlier used postgresql.Driver but 7.0 onwards uses
org.postgresql.Driver
Peter
--
Peter Mount
Enterprise Support Officer, Maidstone Borough Council
Email: petermount@maidstone.gov.uk
WWW: http://www.maidstone.gov.uk
All views expressed within this email are not the views of Maidstone Borough
Council
-----Original Message-----
From: tony [mailto:tony@uickarate.com]
Sent: Thursday, November 16, 2000 2:55 PM
To: pgsql-interfaces
Subject: [INTERFACES] JDBC Problem
I have a problem with loading the JDBC Driver.
So far, my java code does nothing but to load the driver, and
it gives SQLException with message "No suitable driver".
I made the postgresql.jar with
>make jdbc2
(because I am using jdk1.3)
and I used
>jar tf postgresql.jar
to make sure that the driver was included.
(postgresql/Driver.class)
My CLASSPATH is following:
:/usr/local/lib/postgresql.jar:/usr/local/jdk1.3/bin/:/home/tony/classes/
I am trying to load the driver by doing
>Class.forName("postgresql.Driver");
This is under linux platform. Please let me know what could be
wrong if you see anything wrong.
Thanks!
^ permalink raw reply [nested|flat] 17+ messages in thread
* RE: JDBC Problem
@ 2000-11-17 07:18 Peter Mount <petermount@maidstone.gov.uk>
0 siblings, 0 replies; 17+ messages in thread
From: Peter Mount @ 2000-11-17 07:18 UTC (permalink / raw)
To: 'tony' <tony@uickarate.com>; pgsql-interfaces
What have you got your classpath set to?
--
Peter Mount
Enterprise Support Officer, Maidstone Borough Council
Email: petermount@maidstone.gov.uk
WWW: http://www.maidstone.gov.uk
All views expressed within this email are not the views of Maidstone Borough
Council
-----Original Message-----
From: tony [mailto:tony@uickarate.com]
Sent: Thursday, November 16, 2000 3:24 PM
To: pgsql-interfaces
Subject: Re: [INTERFACES] JDBC Problem
Michael, Peter, Chris,
Thanks for the advice. I forgot to mention that
I tried org.postgresql.Driver and it didn't work...
Tony
----- Original Message -----
From: "Michael Stephenson" <mstephenson@tirin.openworld.co.uk>
To: "tony" <tony@uickarate.com>
Cc: "pgsql-interfaces" <pgsql-interfaces@postgresql.org>
Sent: Thursday, November 16, 2000 11:12 AM
Subject: Re: [INTERFACES] JDBC Problem
> > I am trying to load the driver by doing
> > >Class.forName("postgresql.Driver");
>
> Try:
>
> Class.forName("org.postgresql.Driver");
>
> Hope this helps
>
> Michael Stephenson
>
>
^ permalink raw reply [nested|flat] 17+ messages in thread
* JDBC problem
@ 2001-06-18 00:50 Weiming He <weiming@cnri.reston.va.us>
0 siblings, 0 replies; 17+ messages in thread
From: Weiming He @ 2001-06-18 00:50 UTC (permalink / raw)
To: pgsql-interfaces
Hi,
I'm experiencing problems with the jdbc driver. First of all, what is
the correct syntax for running the compiled examples of Postgresql
7.1.2. I ran the followings earlier today, and I got the same error
messages
>java uk.org.retep.finder.Main
Exception in thread "main" java.lang.NoClassDefFoundError:
uk/org/retep/finder/Main
>java basic jdbc:postgresql:cnri_handle loginame passwd
Exception in thread "main" java.lang.NoClassDefFoundError:
jdbc:postgresql:cnri_handle
>java -Djdbc.drivers=org.postgresql.Driver uk.org.retep.finder.Main
Exception in thread "main" java.lang.NoClassDefFoundError:
uk/org/retep/finder/Main
can anyone help me out with this? Thanks in advance.
^ permalink raw reply [nested|flat] 17+ messages in thread
end of thread, other threads:[~2001-06-18 00:50 UTC | newest]
Thread overview: 17+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2000-04-04 09:07 JDBC Problem Michael Yeung <michaely@alphanet.net.au>
2000-08-22 11:46 JDBC problem BogdanKRomski <b.kromski@gaschka.pl>
2000-08-24 23:15 ` Re: JDBC problem John McKown <jmckown@prodigy.net>
2000-08-25 08:49 ` Re: JDBC problem Cedar Cox <cedarc@visionforisrael.com>
2000-08-25 14:35 ` Re: JDBC problem Ross J. Reedstrom <reedstrm@rice.edu>
2000-08-25 17:43 ` Re: JDBC problem John McKown <jmckown@prodigy.net>
2000-08-27 06:04 ` Re: JDBC problem Cedar Cox <cedarc@visionforisrael.com>
2000-08-27 18:36 ` Re: JDBC problem Joachim Achtzehnter <joachim@kraut.bc.ca>
2000-08-28 05:52 ` Re: JDBC problem Cedar Cox <cedarc@visionforisrael.com>
2000-08-25 06:31 RE: JDBC problem Peter Mount <petermount@it.maidstone.gov.uk>
2000-08-25 11:21 RE: JDBC problem Peter Mount <PeterM@maidstone.gov.uk>
2000-11-16 14:54 JDBC Problem tony <tony@uickarate.com>
2000-11-16 16:12 ` Michael Stephenson <mstephenson@tirin.openworld.co.uk>
2000-11-16 15:23 ` tony <tony@uickarate.com>
2000-11-16 16:14 RE: JDBC Problem Peter Mount <petermount@maidstone.gov.uk>
2000-11-17 07:18 RE: JDBC Problem Peter Mount <petermount@maidstone.gov.uk>
2001-06-18 00:50 JDBC problem Weiming He <weiming@cnri.reston.va.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox