| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Jan Wieck" <JanWieck(at)yahoo(dot)com> |
| Cc: | "James Buchanan" <jamesb(at)northnet(dot)com(dot)au>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | RE: place for newbie postgresql hackers to work |
| Date: | 2001-06-07 02:14:13 |
| Message-ID: | ECEHIKNFIMMECLEBJFIGGEONCAAA.chriskl@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > Why not start with Thomas Swan's earlier posting?:
>
> Because first, exactly that would require a good concept and
> (at least I expect it to) a fair amount of system catalog
> changes - not the best *newbe* starter.
>
> I like the idea though. Let the experienced developers
> identify *legwork* TODO items.
From what I can see - there are none. It took me months of reading the
PostgreSQL source code before I could muck with it. (And I still just did
it for fun!) Even the 'basic' stuff like psql and pg_dump modifications
require a knowledge of how foreign keys are stored...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-06-07 02:19:42 | Re: behavior of ' = NULL' vs. MySQL vs. Standards |
| Previous Message | Christopher Kings-Lynne | 2001-06-07 02:10:12 | RE: ORDER BY Problem... |