2013/10/22 Stephen Frost :
>> You also mentioned an external CMS. Any suggestions?
>
> I'm a big fan of git, but if you really want to keep things in-database
> and track dependencies, etc, it occurs to me that you might be able to
> use an actual table in the database to store the raw form of you
Brian,
* Brian Crowell (br...@fluggo.com) wrote:
> On Sun, Oct 20, 2013 at 4:24 PM, Tom Lane wrote:
> > No, and it's very unlikely that there ever will be, because it's
> > completely against the system structure at a number of levels. However,
> > there's more than one way to skin this cat. Ma
2013/10/21 Brian Crowell
> On Sat, Oct 19, 2013 at 11:37 PM, Pavel Stehule
> wrote:
> > For my work is very significant @a point - I wrote and I am writing
> usually
> > database centric stored procedures centric applications and @a works
> > perfect. For me a SQL code is code as any other - I u
On Sat, Oct 19, 2013 at 11:37 PM, Pavel Stehule wrote:
> For my work is very significant @a point - I wrote and I am writing usually
> database centric stored procedures centric applications and @a works
> perfect. For me a SQL code is code as any other - I use a my favourite
> editor, I use a GIT
On Sun, Oct 20, 2013 at 7:01 AM, Bill Moran wrote:
> You could adjust your workflow to use something like dbsteward:
> http://dbsteward.org/
Nifty, but without an editor, I don't think I could convince our
developers to author the databases in XML.
--Brian
--
Sent via pgsql-general mailing li
On Sun, Oct 20, 2013 at 4:24 PM, Tom Lane wrote:
> No, and it's very unlikely that there ever will be, because it's
> completely against the system structure at a number of levels. However,
> there's more than one way to skin this cat. Many people keep their DDL as
> text in some external CMS, a
Brian Crowell writes:
> I've run across one thing that would make a transfer difficult. Postgres
> doesn't preserve the source code for views, as far as I can tell. It parses
> them and then prints them its own way. We have a lot of complicated views,
> where both the formatting and the comments a
On Sat, 19 Oct 2013 22:38:28 -0500 Brian Crowell wrote:
> Hello! I'm evaluating PostgreSQL as a replacement for SQL Server in our
> in-house systems. I've been really impressed with it so far, and I'm eager
> to try it with our data sets.
>
> I've run across one thing that would make a transfer
Hello
2013/10/20 Brian Crowell
> Hello! I'm evaluating PostgreSQL as a replacement for SQL Server in our
> in-house systems. I've been really impressed with it so far, and I'm eager
> to try it with our data sets.
>
> I've run across one thing that would make a transfer difficult. Postgres
> do
On 20/10/13 16:38, Brian Crowell wrote:
Hello! I'm evaluating PostgreSQL as a replacement for SQL Server in
our in-house systems. I've been really impressed with it so far, and
I'm eager to try it with our data sets.
I've run across one thing that would make a transfer difficult.
Postgres doe
Hello! I'm evaluating PostgreSQL as a replacement for SQL Server in our
in-house systems. I've been really impressed with it so far, and I'm eager
to try it with our data sets.
I've run across one thing that would make a transfer difficult. Postgres
doesn't preserve the source code for views, as f
11 matches
Mail list logo
