On Sun, 8 Jul 2001, Ola Sundell wrote:
On Tue, 26 Jun 2001, Dave Cramer wrote:
Ola,
How are you planning on determining if the underlying data has been
changed by some other process? There is a system column called xmin
which can be used, however you will have to add it to the
[[[ Original Message from Tom Lane [EMAIL PROTECTED] ]]]
[EMAIL PROTECTED] writes:
Okay here's a context diff against CVS for getting table privileges.
This appears not to be correct for current sources --- the privilege
set has changed since 7.1.
Ah you probably know better than me. It
Steve Wampler wrote:
...
Too much data was received.
at org.postgresql.PG_Stream.ReceiveString(PG_Stream.java:306)
at org.postgresql.Connection.ExecSQL(Connection.java:532)
at org.postgresql.jdbc2.Statement.execute(Statement.java:294)
at
[[[ Original Message from Peter Eisentraut [EMAIL PROTECTED] ]]]
The list of columns you return is wrong. There is no COLUMN_NAME column.
Does PostgreSQL actually support privileges for individual columns?
TABLE_CAT should be filled in with the database name (should be available
via
Does anyone have some handy metrics of the performance advantage of
prepared vs unprepared statements? I'm considering the case of an
application which has to make multiple queries/inserts (30-100) per
application transaction and which is currenlty generating the sql by
building the strings on
Perpared statements in postgres jdbc are converted on the java side and
then shipped to the backed, so there will no performance increase.
Sheer El-Showk wrote:
Does anyone have some handy metrics of the performance advantage of
prepared vs unprepared statements? I'm considering the case of
Joseph Shraibman wrote:
snip
to do Bad Things. The java.policy file can have an entry to allow only
code in org.postgres to add shutdown hooks (maybe we should put this in
the documentation).
grant codeBase file:///usr/local/pgsql/share/java/ {
permission java.lang.RuntimePermission
Ned Wolpert wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09-Jul-2001 Joseph Shraibman wrote:
BTW having to add a line to your permission file for shutdown hooks is
not a good reason to get rid of this feature. It most cases it would be
Very true. However, having a
