On Oct 8, 10:48 am, Taavi Burns wrote:
> On Oct 8, 9:58 am, "goo...@venix.com" wrote:
>
> >http://www.google.com/url?sa=D&q=http://groups.google.com/group/sqlal...
>
> > I had grumbled that mapping tinyint(1) to bool was an issue for people
> > who were simply trying to process small integers. I
On Oct 8, 9:58 am, "goo...@venix.com" wrote:
> http://www.google.com/url?sa=D&q=http://groups.google.com/group/sqlalchemy/browse_thread/thread/b9c020804456f066/c0a817c7f2133bbe&usg=AFQjCNGDNc-jptHjVeCKGE6qIa_Duh6YBw
>
> I had grumbled that mapping tinyint(1) to bool was an issue for people
> who w
On Oct 7, 9:21 pm, Taavi Burns wrote:
> We use reflection to generate base declarative class definitions of
> our tables, and I'm working on porting from SQLAlchemy 0.5 to 0.6.
> TIMESTAMP column reflection was quite a bit fishy in 0.5, and is
> overall better in 0.6. Still, I found a bug while r
