[GENERAL] Schemas - alter table

Hi everybody, i'm looking for the way to change the schema of a table. I've lots of tables (400), each of these being on the public schema, and, willing to organize this a little bit, i'd like to use some schemas (20). But i seem to be unable to find this in the documentation ; is there a command

[GENERAL] How to add an INHERITS to an already populated table ?

Hi everybody, is it possible to add some inheritance lively, without doing a dump/restore ? Some bits of information to explain why I'd like to do that : I've got those big tables, without correct constraints, sometimes even without foreign keys et with sometimes some problems of data corruption,

Re: [GENERAL] How to add an INHERITS to an already populated table

Well, it seems very promising ! I think I'll make some tests and do it your way asap. Thanks a lot ! Thanks to everybody else, too. Best regards, David -- [EMAIL PROTECTED] - tel: 01.46.47.21.33 - fax: 01.46.47.21.37 ---(end of broadcast)--- TIP

Re: [GENERAL] How to add an INHERITS to an already populated table

> Please note that the inheritance is not fully set -- if you discover > strange behavior e.g. when altering any of the tables, don't be > surprised. In particular, you should set the attislocal and attinhcount > attributes in pg_attribute for the child tables; also pg_depend entries > are missing

[GENERAL] Is a primary key made of a couple columns so much better than a unique() constraint ?

ion is : is it better, in so far as only the database is concerned, to have a primary key than a unique() contraint on a couple columns ? Thanks in advance for your answers, David -- David Pradier -- Directeur Technique de Clarisys Informatique -- Chef de projet logiciels libres / open-source

Re: [GENERAL] Is a primary key made of a couple columns so much better than a unique() constraint ?

> In PostgreSQL, both primary keys and UNIQUE constraints are implemented > via UNIQUE indexes, ergo there is no difference... Thanks Martijn, it's exactly what i wanted to know. Best regards, David -- David Pradier -- Directeur Technique de Clarisys Informatique -- Chef de projet

Re: [GENERAL] Is a primary key made of a couple columns so much better than a unique() constraint ?

st say > "REFERENCES mytab" instead of spelling out "REFERENCES mytab(keycol)". > So "UNIQUE + NOT NULL" is pretty dang close to the same as "PRIMARY > KEY", but not quite. > regards, tom lane Thanks too, Tom :-) Best regards

Re: [GENERAL] Anyone know of a Schema Comparer

pt which can subsequently be executed ? We have > looked at EMS comparer and few others but all seem to compare one entire > db with another. > > > > Regards > > > > Paul Newman > -- David Pradier -- Directeur Technique de Clarisys I

[GENERAL] How to make a good documentation of a database ?

s somebody know the right way to do this ? Best regards, David Pradier -- [EMAIL PROTECTED] - tel: 01.46.47.21.33 - fax: 01.45.20.17.98 ---(end of broadcast)--- TIP 8: explain analyze is your friend

Re: [GENERAL] How to make a good documentation of a database ?

"Comments" in the "table of columns". But I guess it isn't wise nor feasible, is it ? On Thu, Nov 18, 2004 at 09:10:19AM -0600, Timothy Perrigo wrote: > Autodoc might be useful: http://www.rbt.ca/autodoc/ > > > On Nov 18, 2004, at 8:31 AM, David Pradier wrote:

Re: [GENERAL] How to make a good documentation of a database ?

On Thu, Nov 18, 2004 at 03:02:59PM +, Matt wrote: > > The problem is, I don't want to use a lot of time to maintain this > > documentation, and above all, I'd prefer not to insert the information > > twice (read: a new constraint in the database should automagically > > update the documentation

Re: [GENERAL] How to make a good documentation of a database ?

On Thu, Nov 18, 2004 at 04:22:28PM +, Richard Huxton wrote: > David Pradier wrote: > >In fact, I have already looked a little into the tables of PostgreSQL > >itself > >to see if I could hack it by adding a column "Comments" in the "table of > >

Re: [GENERAL] How to make a good documentation of a database ?

Thanks to everybody, Matt, Timothy, Richard, Csaba, Chris and George for your help :-) Finally, I think the right way to go for me is to generate an html output with postgresql-autodoc and make it accessible to every developer. Thanks a lot for your help ! -- [EMAIL PROTECTED] - tel: 01.46.47.2

Re: [GENERAL] How to make a good documentation of a database ?

Yes, it seems interesting. (Is import of sql database possible ?) But for now, I'll stick to postgresql_autodoc. Thanks all the same, Bill, I'll try to keep an eye on this project. On Thu, Nov 18, 2004 at 04:55:06PM +, Bill Harris wrote: > [EMAIL PROTECTED] (David Pradier) write