Thread: A wanna be

"Dave Page" writes:
> As many of you will know, I recently placed a news item on
> www.postgresql.org to try to get some new developers working on
> psqlODBC. I was pleseantly surprised to find that after just a few days
> I had received eight responses from people interested in joining the
> project. This message has been BCC'd to them.

This is really, really good news. With you and Hiroshi both pretty much
withdrawn from development, I was afraid psqlODBC would die on the vine.
(I have no time to contribute to it either :-()

One comment on your todo list:

> 3) An audit of the code for possible buffer overrun problems should be
> undertaken.

I think this is really critical and should be done ASAP. We already
have at least one known issue of this kind. The bad news of courseis that it is boring, tedious work ... but on the other hand it's a
great way to learn one's way around the code. I hope that several of
the new developers will perform such reviews.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

I'm not a postgres developer.. and really, all of this information is on the 
postgres website.. But I liked reading PostgreSQL by Korry Douglas and Susan 
Douglas (ISBN: 0735712573) which gave me all the information I needed about 
PostgreSQL itself as well as the various API's. I found them pretty easy to 
understand and use. I'm also a C programmer (novice) and the C api (libpq) is 
pretty easy to understand if you understand databases.

However, I seem to work better having hard bound copies I can read in meetings 
and carry with me. The online documentation is far superior than some of the 
competing products, I would certainly start there.

http://www.postgresql.org/docs/7.4/static/libpq.html

-netmask

> Jaime Casanova (systemguards@yahoo.com) composed today:

> Hi all,
>
> I'm a young developer with some knowledge in various programming languages including C. Nowadays, i'm not capable to
contributeto any part of the postgresql project but i want seriously learn what i need in order to contribute.
 
> Can you guys tell me where can i start?
> Where can i find usefull information about Databases programming techniques?

On Thursday 01 July 2004 01:10 pm, Jaime Casanova wrote:
>
> I'm a young developer with some knowledge in various programming
> languages including C. Nowadays, i'm not capable to contribute to any
> part of the postgresql project but i want seriously learn what i need in
> order to contribute. Can you guys tell me where can i start?
> Where can i find usefull information about Databases programming
> techniques?
>

First, become intimately familiar with the tool from the user's perspective. 
I use PostgreSQL for some major projects, and so I have grown familair with 
it. I don't think I could've gotten this familiar without having to 
actually use it in a production environment.

Second, start coding extensions to it. I have written C code for both the 
client and server side, and have learned tremendously from that.

Finally, start reading code around the parts you are interested in.

I have also found that watching the patches come in will give you a feel for 
what is happening. Not only do you see the actual code, but you can watch 
the experts talk about it. You can read through the code and then watch as 
the server behaves differently. It's pretty amazing.

-- 
Jonathan Gardner
jgardner@jonathangardner.net

The developer's FAQ is a good place to start.

---------------------------------------------------------------------------

Jonathan Gardner wrote:
> On Thursday 01 July 2004 01:10 pm, Jaime Casanova wrote:
> >
> > I'm a young developer with some knowledge in various programming
> > languages including C. Nowadays, i'm not capable to contribute to any
> > part of the postgresql project but i want seriously learn what i need in
> > order to contribute. Can you guys tell me where can i start?
> > Where can i find usefull information about Databases programming
> > techniques?
> >
> 
> First, become intimately familiar with the tool from the user's perspective. 
> I use PostgreSQL for some major projects, and so I have grown familair with 
> it. I don't think I could've gotten this familiar without having to 
> actually use it in a production environment.
> 
> Second, start coding extensions to it. I have written C code for both the 
> client and server side, and have learned tremendously from that.
> 
> Finally, start reading code around the parts you are interested in.
> 
> I have also found that watching the patches come in will give you a feel for 
> what is happening. Not only do you see the actual code, but you can watch 
> the experts talk about it. You can read through the code and then watch as 
> the server behaves differently. It's pretty amazing.
> 
> -- 
> Jonathan Gardner
> jgardner@jonathangardner.net
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
> 
> 
> !DSPAM:40e4b35d139131332413006!
> 
> 

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073