On Fri, 24 Jan 2003 05:56, you wrote:
> Is there a query that will return all the databases available, similar
> to what psql -l does?
select * from pg_database;
Horst
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On Wed, 16 Oct 2002 19:15, John Geng wrote:
> how to migrate sql from MS sql server to postgresql?
> i'd like to tranfer sql schema from MS server
> Example:
> ***1*
> if exists (select * from sysobjects
> where id = object_id(N'[admin].[test]') and
>
On Saturday 20 October 2001 08:53, you wrote:
> Andre,
>
> The only reason to have data for one query in different databases is if
> the databases are on different machines. If you're running on PC-type
> hardware, you might have to do that some times for performance reasons.
> But if at that poin
On Thursday 25 October 2001 03:41, John Hasler wrote:
> Josh writes:
> > I'm sure you could make your own GUID, whatever one is.
>
> Globally Unique IDentifier, probably. Just hash a 128 bit random number
> with the current date.
That gives you no gurantee it will be unique.
What we are using i
On Saturday 18 August 2001 00:18, you wrote:
> I have encountered this problem (in a different context), and could not
> find a way to insert entire rows/records in the way that you appear to
> want. But it worked fine if I INSERTed explicitly, like:
> INSERT INTO table VALUES (OLD.field1, OLD.fi
I have difficulties understanding how to use variable of "record" or "row"
type. How do I actually insert the variables OLD or NEW or a record type into
a table from within a trigger?
Like doing the following:
drop table th1;
create table th1(
id serial,
text text );
drop table th_audit;
crea
Help please!
How do I actually insert the variables OLD or NEW or a record type into a
table from within a trigger?
Like doing the following:
drop table th1;
create table th1(
id serial,
text text );
drop table th_audit;
create table th1_audit(
ts timestamp default now()
) inherits(th1);
dr
