Re^2: Advice of picking the language for my job, please

Perl exists as a built-in tool to postgreSQL, it's called pl/perl. See PL/Perl documentation from postgres website
It's simply that using DBI to interface postgres to perl is NOT the best way; but perl integrates extremely tightly and efficiently to postgres.

Comment on Re^2: Advice of picking the language for my job, please

Replies are listed 'Best First'.
Re^3: Advice of picking the language for my job, please by Anonymous Monk on Feb 05, 2005 at 19:50 UTC
I've been thinking of using Perl with PostgreSQL recently for a proejct. Can you tell me why DBD::Pg is any less efficient than DBD::mysql?	[reply]
Re^4: Advice of picking the language for my job, please by wazoox (Prior) on Feb 06, 2005 at 11:24 UTC
I wouldn't say that. Actually postgreSQL is much more powerful than MySQL, so you'll more often hit the limits of DBI/DBD using postgres than Mysql...	[reply]
Re^4: Advice of picking the language for my job, please by redhotpenguin (Deacon) on Feb 07, 2005 at 05:42 UTC
This issue recently came up on the mod_perl list. I brought the issue to the PostgreSQL irc channel and apparently libpq doesn't return rows individually as you might expect, instead loading the data into memory and then returning them one by one on a fetch basis IIRC. See this thread for a summary of the issue and a suggested solution using cursors in conjunction with DBI to handle retrievals of many rows from a PostgreSQL database.	[reply]