Hi,
I'm working on the new release of ColanderAlchemy (
https://github.com/stefanofontanelli/ColanderAlchemy ) which will use
the new SQLA 0.8 inspection API.
The new version of CA will use 'info' kwarg which can be specified in
both Column and relationship.
I found also 'info' kwargs in
Hello,
I have below use where
Employer and EmployerPhone the one emp can have multiple phone number out
of which at any given point of time there should be
only one 'is_active' due to concurrency load, emp_phone got multiple
'is_active' as 'Y' in emp_phone i want to update the emp_phone table
On Oct 12, 2012, at 5:10 AM, Stefano Fontanelli wrote:
Hi,
I'm working on the new release of ColanderAlchemy (
https://github.com/stefanofontanelli/ColanderAlchemy ) which will use the new
SQLA 0.8 inspection API.
The new version of CA will use 'info' kwarg which can be specified in
Il 12/10/12 17.38, Michael Bayer ha scritto:
On Oct 12, 2012, at 5:10 AM, Stefano Fontanelli wrote:
2) Is access of Column.info the right way to 'read' Column.info specified by
the user in declarative example?
if you want to get at the .info on Column then yes, but for your purposes it's
On Oct 12, 2012, at 9:40 AM, Praveen wrote:
Hello,
I have below use where
Employer and EmployerPhone the one emp can have multiple phone number out of
which at any given point of time there should be
only one 'is_active' due to concurrency load, emp_phone got multiple
'is_active' as
On Tuesday, October 9, 2012 10:19:34 PM UTC+8, Michael Bayer wrote:
yeah, the whole FreeTDS story is awful, I don't understand any of it
either. I'm still at wave a dead chicken stage with FreeTDS (
http://dictionary.reference.com/browse/wave+a+dead+chicken).
The ODBC Driver 1.0 for
