Re: [HACKERS] what to do with backend flowchart

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Robert Treat" <xzilla(at)users(dot)sourceforge(dot)net>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>, <pgsql-www(at)postgresql(dot)org>
Subject: Re: [HACKERS] what to do with backend flowchart
Date: 2005-03-22 09:11:13
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E472BCE1@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-www

> -----Original Message-----
> From: pgsql-hackers-owner(at)postgresql(dot)org
> [mailto:pgsql-hackers-owner(at)postgresql(dot)org] On Behalf Of Robert Treat
> Sent: 21 March 2005 19:05
> To: Tom Lane
> Cc: pgsql-hackers(at)postgresql(dot)org; pgsql-www(at)postgresql(dot)org
> Subject: Re: [HACKERS] what to do with backend flowchart
>
> My thoughts were that it is certainly easier for us to
> implement web code that
> comes from the web cvs rather than the core cvs, and also
> that it seems wierd
> to have this type of html/graphics living tucked away inside
> the application
> code. You seem to be opposed to moving it though (or at
> least unconvinced)
> so I guess we will work things out on the web side.

It wouldn't be the first thing we suck from the core CVS for the web. If
it's just a case of keeping the correct set of files up to date on the
webside, let me know what they are and I'll set it up for you Robert.

/D

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2005-03-22 11:31:55 Failed to re-find parent key
Previous Message strk 2005-03-22 09:07:40 Re: caches lifetime with SQL vs PL/PGSQL procs

Browse pgsql-www by date

  From Date Subject
Next Message Magnus Hagander 2005-03-22 10:25:42 Re: Fwd: PostgreSQL Consultants List
Previous Message Josh Berkus 2005-03-21 20:03:47 Fwd: PostgreSQL Consultants List