Re(2): [SQL] Large Object dump ?

You can try the script I made for exporting all my Pg database. Ideas were borrowed from pg_dumplo-0.0.5. Make it sure that you have "Perl5 extension for PostgreSQL - Pg.pm" installed. sherwin #!/usr/bin/perl -w # # Export large objects of all Pg database # - Sherwin T. Daganato ([EMAIL PROTEC

Re: Re(2): [SQL] Large Object dump ?

On Wed, 1 Nov 2000, pgsql-sql wrote: > You can try the script I made for exporting all my Pg database. > Ideas were borrowed from pg_dumplo-0.0.5. > Make it sure that you have "Perl5 extension for PostgreSQL - Pg.pm" > installed. Why you re-write pg_dumplo to perl and not use directly it? Perl

Re: [SQL] Outer Joins

Marc, I did not look at your queries, but outer joins are supported in the latest development version of PostgreSQL, and will be supported in the upcoming 7.1 release of the software - beta due soon. Regards, Grant Marc Rohloff wrote: > I've been looking at the open-source databases for a pr

Re(2): Re(2): [SQL] Large Object dump ?

because of some problems (see below). i was also thinking that it was just a compatibility problem of pg_dumplo-0.0.5 to postgresql 6.5.3. and because i needed it badly, i wrote a "quick & dirty" perl script. 1. When I tried showing all LO of my_db, I got this message: pg_dumplo -w -d my_db N

Re: [SQL] Problem with coalesce..

Try:   SELECT COALESCE(CURVALUE,1) FROM TABLEKEYS WHERE TABLENAME = 'BUYER';   - Original Message - From: George Henry C. Daswani To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, October 31, 2000 5:52 PM Subject: [SQL] Problem with coalesce..

Re: [SQL] Outer Joins

Marc, > select a.col1, b.col2 from a,b > where a.col1 = b.col2 >or b.col2 is null The above would select each record in a that matched a record in b, plus each record in b for every possible a where b.col2 was null - not where there was no match. > select a.col1, b.col2 from a,b > where a.

[SQL] Timespan / interval calculations?

I'm using PostgreSQL 6.5. I have a table with a timestamp field. I want to extract all rows with a timestamp less then an hour ago. I've tried several things, but nothing seem to work. How should it be done? I've tried select * from syslog where stamp between timestamp('now') - inte

Re: [SQL] INSERT [IGNORE] INTO TABLE

The proper fix for this is subtransactions, which we will have someday. You do the INSERT in a subtransaction. > Edmar Wiggers wrote: > > > > If I try to insert some row which in the table already exist the > > > postgre don't insert it and tell some error. Everything ok. > > >

Re: [SQL] Outer Joins

>> select a.col1, b.col2 from a,b >> where a.col1 = b.col2 >>or a.col1 not in (select b.col2 from b) >This would work, but it would be *much* slower than a UNION query. "Not >In" queries are perhaps the slowest you can run; see the earlier thread >"Query Problem" for a discussion. UNION qu

Antw: [SQL] Outer Joins

>>> "Marc Rohloff" <[EMAIL PROTECTED]> 01.11.2000 09.02 Uhr >>> > > select a.col1, b.col2 from a,b > where a.col1 = b.col2 > or b.col2 is null > This query has nothing to do with an outer join. See the following example: table a c1 --- x y and table b c2 --- x Then an outer join give

[SQL] Re: [GENERAL] Problem with coalesce..

There are still some contexts in which subqueries in expressions are wierd. The example below appears to work in current sources however. Stephan Szabo [EMAIL PROTECTED] On Tue, 31 Oct 2000, George Henry C. Daswani wrote: > Hello, > > Was wondering if such a call is unsupported, or a bug?