On Wednesday, May 6, 2015 at 8:03:54 PM UTC-7, Michael Bayer wrote:
Well it's already weird that you're defining both default and
server_default at the same time on the Column. I'm not actually sure
what effect that would have and am surprised it doesn't fail in some
way...or at least
On 5/7/15 9:10 AM, jo wrote:
Hi all,
I would like to create a python customer function to extract data from a
table column and return a calculated value as in:
def birth(data):
mm =
dict(A='01',B='02',C='03',D='04',E='05',H='06',L='07',M='08',P='09',R='10',S='11',T='12')
SQLAlchemy release 1.0.4 is now available.
With release 1.0.4 we are pretty much through all the bumps we had in
the 0.9 to 1.0 movement. Four additional very minor regressions are
solved in this release. Most prominently, another issue regarding recent
enhancements to the
SQLAlchemy release 1.0.4 is now available.
With release 1.0.4 we are pretty much through all the bumps we had in
the 0.9 to 1.0 movement. Four additional very minor regressions are
solved in this release. Most prominently, another issue regarding recent
enhancements to the
Hi all,
I would like to create a python customer function to extract data from a
table column and return a calculated value as in:
def birth(data):
mm =
dict(A='01',B='02',C='03',D='04',E='05',H='06',L='07',M='08',P='09',R='10',S='11',T='12')
return '19'+data[6:8] +'-'+
