[GENERAL] PostgreSQL v7.1.2 Now Available ...

Just a quick announcement that v7.1.2 is now available for download ... primarily a bug fix release, the following changes have been made: Changes --- Fix PL/PgSQL SELECTs when returning no rows Fix for psql backslash core dump Referential integrity permission fix Optimizer fixes pg_dump cle

Re: [GENERAL] Trouble with strange OUTER JOIN syntax

Hi Tom, > > How would you translate the following SELECT statements with > > outer joins to PostgreSQL syntax? > > > SELECT ... > > FROM tab1 alias_tab1, tab2 alias_tab2, > >OUTER ot1 alias_ot1, > >OUTER ot2 alias_ot2 > > WHERE ... > > > SELECT > > FROM tab1 alias_tab1, ta

Re: [GENERAL] COPY with default values?

You are correct and if you did your bulk insert with INSERT commands, it will work just fine. The difference is the COPY command which AFAIK was/is intended for backup and restore use. len morgan -Original Message- From: Jeff Boes <[EMAIL PROTECTED]> To: Postgres-general <[EMAIL PROTECT

Re: [GENERAL] Username with a hyphen character (grant failing?)

> > What's the scoop with username constraints? I setup and > > created a user with a '-' character in the middle (worked). > > Double quotes are your friend when dealing with names that don't > follow the usual constraints for identifiers. Are single quotes treated differently than

Re: [GENERAL] COPY with default values?

On Fri, 25 May 2001 10:33:41 -0400 Tom Lane <[EMAIL PROTECTED]> wrote: > COPY does not deal with insertion of default values. Sorry. This seems odd to me, especially since Pgsql treats INSERT INTO keywords (key_id, key_text) VALUES (null, 'foo'); differently than INSERT INTO keywords (key_te

Re: [GENERAL] COPY with default values?

Jeff Boes <[EMAIL PROTECTED]> writes: > Now I would like to initialize this table with a COPY statement, but > without supplying values for the primary key. COPY does not deal with insertion of default values. Sorry. One rather klugy answer is to COPY to a temp table that has only the columns y

[GENERAL] [URGENT] How to generata a unique string id

Hi, I need to generate a unique four letters string (p.e ,AAAB) for any tuple I insert into a table, any idea ? How can I do this ? Thanks. -- Manuel Durán Aguete ALSERNET 2000 S.L http://www.alsernet.es Tlf: 902 187 187 Fax

Re: [GENERAL] Username with a hyphen character (grant failing?)

Sean Chittenden <[EMAIL PROTECTED]> writes: > What's the scoop with username constraints? I setup and > created a user with a '-' character in the middle (worked). Double quotes are your friend when dealing with names that don't follow the usual constraints for identifiers.

Re: [GENERAL] COPY with default values?

I believe COPY is limited to reading ENTIRE records into a table not pieces of them. len morgan -Original Message- From: Jeff Boes <[EMAIL PROTECTED]> To: Postgres-general <[EMAIL PROTECTED]> Date: Friday, May 25, 2001 9:20 AM Subject: [GENERAL] COPY with default values? >Let's say I h

[GENERAL] COPY with default values?

Let's say I have a table of keywords, with a SERIAL primary key. CREATE TABLE keywords ( key_id SERIAL PRIMARY KEY, key_text TEXT ); Now I would like to initialize this table with a COPY statement, but without supplying values for the primary key. In other words, how can I use COPY to perfo

[GENERAL] pl-perl setup?

Hello, I'm fairly new to PostgreSQL. Does anyone have a resource for setting up plperl from scratch? The online documentation doesn't offer much help. -- Jeff Boes vox 616.226.9550 Database Engineer fax 616.349.9076

[GENERAL] Transactions and *ABORT STATE*

I were testing out (using psql) transactions and locking in postgresql using only BEGIN/UPDATE(on a specific table)/COMMIT&ROLLBACK and notices several time that instead of waiting it went into *ABORT STATE*. Why is this? Also I notice that COMMIT'ing a deadlock'ed transaction did nothing but a

[GENERAL] Username with a hyphen character (grant failing?)

What's the scoop with username constraints? I setup and created a user with a '-' character in the middle (worked). When I tried to grant the new user some privs, grant choked on the '-' w/ a parse error. foo=# GRANT SELECT ON test TO www-foo; ERROR: parser: parse error at or near "-"

[GENERAL] JDBC

Can someone confirm this as a bug or slap me for missing something obvious? # \d foo Table "foo" Attribute | Type | Modifier ---++-- bar | bigint | "UPDATE foo SET bar = 0" works from psql but when I try the same thing via the JDBC driver I get dtoi4:

Re: [GENERAL] Implicit row locking during an UPDATE

On Fri, May 25, 2001 at 02:23:50AM -, Dr. Evil wrote: > > I'm still not understanding this, and it's vitally important to the > project I'm working on, so I have a question: > > >From my understanding, this: > > UPDATE account SET value = 10 WHERE number = 99; > > actually implies all of t