Hi,
The following is a stripped down use case that I have, where I use
single table inheritance and run a query.first(), however I get a
deprecation warning and I was wondering why ??
A minor bug, an instance of SA internally using the deprecated syntax.
Fixed in r3766.
Paul
Paul Johnston wrote:
Hi,
generate the default values (default = _some_python_function_). The
problem is that such function is not saved in the database itsself.
Ok, I wonder, why is this a problem for you? Usually people are happy
with ORM-specific logic (such as this) just being stored
If a process with a reference to an engine (and hence a connection
pool) forks, how can I be sure that the child process closes any
inherited descriptors before creating its own engine and connections?
If the child calls dispose() on an engine it has inherited, the engine
seems to 'dispose' of
On Nov 11, 2007, at 2:55 PM, Jorge Godoy wrote:
One other possibility is to code the default inside a database
trigger.
But then you can't say that you have a NOT NULL column because if
you omit
the value then you'll get an SQL error... (While you can say, for
example, INSERT INTO
On Nov 11, 2007, at 3:58 PM, [EMAIL PROTECTED] wrote:
If a process with a reference to an engine (and hence a connection
pool) forks, how can I be sure that the child process closes any
inherited descriptors before creating its own engine and connections?
If the child calls dispose() on
Michael Bayer wrote:
im fairly certain triggers used to generate INSERT values are
compatible with NOT NULL columns. although in this particular thread
I dont think I understand the issue exactly, it seemed like it was
just asking for some Python function to be executed external to the
I guess you know that storing the actual bytecodes (or the source) of a
Python function in the database itself is not going to buy you much:
Since the function bytecodes or source
would be in Python, only a Python interpreter could run it to produce
the function result, and if you know you're
Also depending on how you are starting the subprocess, you may have control
over open file handle inheritance. The subprocess module, for example allows
you to close all open inherited files, which would include open sockets for
DBAPI connections (or a file handle in the case of SQLite). You could
Ah good thanks: I had noticed that too and was just ignoring it until it
bugged me enough. Laziness pays off again!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email
