On Monday 05 May 2008 14:28:47 Micah Yoder wrote:
> Just started a nice new project in mod_python with psycopg2, then
> discovered that psycopg2 apparently does not support prepared statements.
> Is that true? Any workarounds?
Ah wait, do prepared statements not need any support from t
Just started a nice new project in mod_python with psycopg2, then discovered
that psycopg2 apparently does not support prepared statements. Is that true?
Any workarounds?
That ruins my whole day ...
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your
On Tuesday 15 April 2008 10:27:14 am Dawid Kuroczko wrote:
> Whch would you suggest?
> How do they differ?
Sorry to bring this back up (I try to keep up with this list but it's hard!),
but isn't licensing a concern?
If I understand correctly, pygresql is BSD-licensed, but depends on MX which
is
Thanks for the replies. That's kind of what I figured, though it would be
interesting if it were possible. For example, if a financial institution
could allow their clients direct connections to a database, the clients (or
anyone) could build absolutely any interface to it they want. I think
Just curious, would PostgreSQL be considered secure for applications involving
financial matters where the clients have a direct database logon?
First, to clarify, I'm not in a serious position to write such an application.
I'm just wondering. :-) If it is possible, I may make a proof of conc
speed up to where I was fairly happy with it.
If there's a better solution than that, I'm not aware of it.
But like someone else mentioned, it's not quite "practical" database usage.
--
Like to travel?http://TravTalk.org
Mic
leave Red Hat the main (only?) commercial supporter of PostgreSQL?
Not that it really needs expensive support. I'm finding that it just works.
Maybe THAT was the problem... :-)
Best to all,
Micah
--
Like to travel?http://TravTalk.org
Micah Yoder Internet
