Re: [ADMIN] empty a database

2005-02-16 Thread Dick Davies
* Christopher Browne <[EMAIL PROTECTED]> [0223 20:23]: > Clinging to sanity, [EMAIL PROTECTED] (Dick Davies) mumbled into her beard: > > Is there a neat way to clean out a database via SQL commands? > > > > i.e. get rid of tables, sequences, integers, etc. > > > > At present I'm using dropdb/create

Re: [ADMIN] empty a database

2005-02-15 Thread Christopher Browne
Clinging to sanity, [EMAIL PROTECTED] (Dick Davies) mumbled into her beard: > Is there a neat way to clean out a database via SQL commands? > > i.e. get rid of tables, sequences, integers, etc. > > At present I'm using dropdb/createdb, but thats' far from ideal > and I think it's causing postgres t

Re: [ADMIN] empty a database

2005-02-15 Thread Brad Nicholson
If there are any foreign key constraints, you'll have to truncate the tables in the appropriate order. You would also have to reset the sequence values as well. Naomi Walker wrote: How about just truncating all the tables? Dick Davies wrote: * Tom Lane <[EMAIL PROTECTED]> [0232 16:32]:

Re: [ADMIN] empty a database

2005-02-15 Thread Naomi Walker
How about just truncating all the tables? Dick Davies wrote: > * Tom Lane <[EMAIL PROTECTED]> [0232 16:32]: > >>Dick Davies <[EMAIL PROTECTED]> writes: >> >>>Is there a neat way to clean out a database via SQL commands? >>>i.e. get rid of tables, sequences, integers, etc. >> >>>At present I'm u

Re: [ADMIN] empty a database

2005-02-15 Thread Dick Davies
* Tom Lane <[EMAIL PROTECTED]> [0232 16:32]: > Dick Davies <[EMAIL PROTECTED]> writes: > > Is there a neat way to clean out a database via SQL commands? > > i.e. get rid of tables, sequences, integers, etc. > > > At present I'm using dropdb/createdb, but thats' far from ideal > > and I think it's

Re: [ADMIN] empty a database

2005-02-15 Thread Tom Lane
Dick Davies <[EMAIL PROTECTED]> writes: > Is there a neat way to clean out a database via SQL commands? > i.e. get rid of tables, sequences, integers, etc. > At present I'm using dropdb/createdb, but thats' far from ideal > and I think it's causing postgres to do more mork than it needs to... Wel