comment on

I have actually done some work with PostgreSQL and PL/Perl about 18 months ago and found the implementation, whilst interesting, somewhat lacking with the performance of this coupling of PostgreSQL and Perl was less than stellar, with, if I remember correctly, the Perl interpreter being launched each time a stored function employing PL/SQL is called. Additionally, I seem to remembering having major issues with concurrency with DBD::SPI, which at the time didn't support transactions anyhow, negating the value of some of the database server-side processing which I was looking to implement with this arrangement.

In short, it's an interesting arrangement, but if you want the integration of your database server to make it more of an "application" server, you would be better served by the exploring the server programming interface with C.

perl -le "print unpack'N', pack'B32', '00000000000000000000001000000000'"

In reply to Re: Perl, PostgreSQL, and Where Things Are Done by rob_au
in thread Perl, PostgreSQL, and Where Things Are Done by Velaki

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


go ahead... be a heretic
	PerlMonks