Re: [SQL] [GENERAL] documenting tables version control

2015-05-06 Thread Steve Midgley
I just use sql tables. But if I represent them outside of pg I usually use migration files which are part of ruby on rails. But sqitch looks good too. Steve On May 6, 2015 7:31 AM, "Suresh Raja" wrote: > Thanks Melvin, Joshua, PT and Steve! > > your information is good. Im looking for creating

Re: [SQL] [GENERAL] documenting tables version control

2015-05-06 Thread Adrian Klaver
On 05/06/2015 07:31 AM, Suresh Raja wrote: Thanks Melvin, Joshua, PT and Steve! your information is good. Im looking for creating a catalog for my application schema. Do you have anything that you use for catalog of your schema. Maybe using excel. Yes Mercurial(mercurial.selenic.com) with S

Re: [SQL] [GENERAL] documenting tables version control

2015-05-06 Thread Steve Midgley
I just use sql tables. But if I represent them outside of pg I usually use migration files which are part of ruby on rails. But sqitch looks good too. Steve On May 6, 2015 7:31 AM, "Suresh Raja" wrote: > Thanks Melvin, Joshua, PT and Steve! > > your information is good. Im looking for creating

Re: [GENERAL] documenting tables version control

2015-05-06 Thread Suresh Raja
Thanks Melvin, Joshua, PT and Steve! your information is good. Im looking for creating a catalog for my application schema. Do you have anything that you use for catalog of your schema. Maybe using excel. Thanks, SR On Tue, May 5, 2015 at 4:42 PM, Melvin Davidson wrote: > Try this query and

Re: [GENERAL] documenting tables version control

2015-05-06 Thread Tim Clarke
On 06/05/15 11:04, Gavin Flower wrote: > See comments at bottom, > > On 06/05/15 20:47, Tim Clarke wrote: >> We keep the DDL statements for any tables in our subversion code >> repository just like any other programming code. Takes only a moment >> then all history or changes is available and compa

Re: [GENERAL] documenting tables version control

2015-05-06 Thread Gavin Flower
See comments at bottom, On 06/05/15 20:47, Tim Clarke wrote: We keep the DDL statements for any tables in our subversion code repository just like any other programming code. Takes only a moment then all history or changes is available and comparable. svnserve on our linux server, svn workbenc

Re: [GENERAL] documenting tables version control

2015-05-06 Thread Tim Clarke
We keep the DDL statements for any tables in our subversion code repository just like any other programming code. Takes only a moment then all history or changes is available and comparable. svnserve on our linux server, svn workbench on my ubuntu laptop, all open source :) Tim Clarke On 05/05/15

Re: [GENERAL] documenting tables version control

2015-05-05 Thread Melvin Davidson
Try this query and see if it fulfills your needs. Adjust the WHERE clause as needed. SELECT table_catalog as database, table_schema as schema, table_name as table, column_name as column, ordinal_position as position, column_default as default, is_nu

Re: [GENERAL] documenting tables version control

2015-05-05 Thread Joshua D. Drake
On 05/05/2015 01:13 PM, Suresh Raja wrote: Hi All: I have tables with different versions in the same schema. Like T1a, T1b, T1c T2a, T2b, T2c, T2d ... etc. I'm interested in documenting various version of tables, may be in excel sheet or may be in another schema in the database. I

Re: [GENERAL] documenting tables version control

2015-05-05 Thread PT
On Tue, 5 May 2015 15:13:42 -0500 Suresh Raja wrote: > > > I have tables with different versions in the same schema. Like > T1a, T1b, T1c > T2a, T2b, T2c, T2d > > ... > etc. > > > I'm interested in documenting various version of tables, may be in excel > sheet or may be in another schema

[GENERAL] documenting tables version control

2015-05-05 Thread Suresh Raja
> > Hi All: I have tables with different versions in the same schema. Like T1a, T1b, T1c T2a, T2b, T2c, T2d ... etc. I'm interested in documenting various version of tables, may be in excel sheet or may be in another schema in the database. I would like to store information on table name