From: Marc Spitzer <marc@oscar.eng.cv.net>
To: pgsql-sql <pgsql-sql@postgresql.org>
Subject: Re: Editor for pgsql
Date: Mon, 22 Jul 2002 19:07:54 -0400
Message-ID: <20020722190754.A11513@oscar.eng.cv.net> (raw)
In-Reply-To: <200207221609.22089.james@lrgmail.com>
References: <web-1586048@davinci.ethosmedia.com>
<200207221609.22089.james@lrgmail.com>
On Mon, Jul 22, 2002 at 04:09:21PM -0400, James Orr wrote:
> On Monday 22 July 2002 12:27 pm, Josh Berkus wrote:
>
> > Me, I use Kate, an MDI text editor from the KDE crew, and CVS for
> > version control. Thanks, KDE guys! But, after 3 years of Postgres,
> > I'm pretty fluent in PL/pgSQL. I even double-quote without thinking
> > about it.
>
> How do you use CVS on your database? I recently started doing this, and i'm
> wondering how other people handle it.
>
> Basically I create a sql folder with three sub-folders tables, views
> and functions. I have a file for each table in tables, each view in
> views and for each trigger and/or function in functions.
>
> For the actual editing? I'm a vi fan myself :). If i'm using the graphical
> vim I can even do CVS operations with a custom menu.
>
> - James
James,
That sounds very ugly, I will usually have 1-4 files per db. Either
everything goes into 1 file, drops at the front then creates. Or
2 files, 1 for ddl( create/drop table) and another for plpgsql procedures
and triggers. Sometimes I will split each of those into a create and drop
file. But that is about as complex as I want it to get.
marc
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: marc@oscar.eng.cv.net
Subject: Re: Editor for pgsql
In-Reply-To: <20020722190754.A11513@oscar.eng.cv.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox