in most cases the DBAPI driver, not SA, is the one returning the
Python datetime objects to you. also like Rick said most DBs are not
going to store an invalid date. so if you arent storing an actual
date, you probably dont want to declare those columns as Date columns.
On Mar 4, 2007,
SA, and rightly so, thinks a date is a date.
So, two approaches:
If you want to guess at the dates, keep the input partial dates as
strings. Use the excellent dateutil package to parse the fuzzy strings
into datetime objects and store those.
If you want to store the fuzzy dates themselves, just
Mel Collins [EMAIL PROTECTED] writes:
As I haven't yet found any other way around this, my only recourse
seems to be to split the date columns into three, which just feels
wrong to me. Can anyone suggest a more elegant solution?
I believe the details of your application should have this
