I think I will start to get into the code slowly. But I agree that a
preprocessor would be fine. I found some old 0.1 code on the internet.
Michael
--
Dr. Michael Meskes, Project-Manager | topsystem Systemhaus GmbH
meskes@topsystem.de | Europark A2, Adenauerstr. 20
meskes@debian.org | 52146 Wuerselen
Go SF49ers! Go Rhein Fire! | Tel: (+49) 2405/4670-44
Use Debian GNU/Linux! | Fax: (+49) 2405/4670-10
> -----Original Message-----
> From: Thomas G. Lockhart [SMTP:lockhart@alumni.caltech.edu]
> Sent: Wednesday, February 04, 1998 3:29 PM
> To: Michael Meskes
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Hi
>
> > 1) Is there an embedded SQL preprocessor available? I read about an
> > alpha version, but is it still maintained?
>
> I remember mention of it on the list a while ago, but have not heard
> anything since. Also, no code for this was contributed for the
> distribution, and it should be included. It would be _great_ to have a
> real
> preprocessor.
>
> > 3) How would you describe the general goal of this project: Offer as
> > good a database system as you can create as free software? That is
> > should it be able to handle huge amounts of data, or is it seen more
> as
> > a tool for a private person/small business?
>
> As scrappy pointed out, we would like to not forget either kind of
> user.
> However, afaik PostgreSQL is the closest to a "heavyweight" RDBMS
> available
> in the freeware world, so if we had to choose we would probably put
> ourselves on the "huge amounts of data" end of the spectrum.
>
> > 4) Are there areas/Which areas need help?
>
> The ToDo has lots of projects. Also, as you get started and learn the
> details of Postgres internals the docs project could use some
> contributions
> :).
>
> There are other areas which are not yet called out in the ToDo list,
> including
>
> - recovery of munged databases (I think disk full conditions may
> cause
> damage)
> - transaction-only and session-only tables, variables, etc.
> - re-think the table/type interface to allow more extensibility of
> types
>
> But, picking simpler items from the ToDo is probably the best way to
> get
> familiar with pieces of the code.
>
> Welcome.
>
> - Tom
