I discovered that case() doesn't produce an ELSE clause when its else_
argument is set to else_=0. This is easily fixed by setting else_='0'
instead, but I wonder if this is ideal behavior.
-Bret.
--~--~-~--~~~---~--~~
You received this message because you are
Hey all,
I have an application which needs to support 'incomplete' dates -
those where the month or day are unknown (or even the year, why not?).
MySQL supports doing this in it's Date column type (I don't know
about other DBs), so for example I can have a date field containing:
1998-10-00.
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
This is a one-liner fix that I already have in my tree. It might be good
practice one to get your feet wet if you want to take a swag at it, Bret...
Rick
On 3/4/07, Bret Aarden [EMAIL PROTECTED] wrote:
I discovered that case() doesn't produce an ELSE clause when its else_
argument is set to
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
I was wondering if it is possible to specify a primary key manually?
The reason I want to do this is I have a Twisted client/server program
where the clients have some of the data from the server. I'd like the
clients to be able to have their own sqlalchemy database with objects
and relationships
