On 21Nov2011 22:18, Roy Smith wrote:
| In article
| <8832ab6d-8def-45d1-92df-baac40e1c...@t36g2000prt.googlegroups.com>,
| alex23 wrote:
| > On Nov 22, 10:25?am, Roy Smith wrote:
| > > Everytime I've worked with SQLAlchemy, I've run away screaming in the
| > > other direction. ?Sure, portabili
In article
<8832ab6d-8def-45d1-92df-baac40e1c...@t36g2000prt.googlegroups.com>,
alex23 wrote:
> On Nov 22, 10:25 am, Roy Smith wrote:
> > Everytime I've worked with SQLAlchemy, I've run away screaming in the
> > other direction. Sure, portability is a good thing, but at what cost?
>
> I've n
On Nov 22, 10:25 am, Roy Smith wrote:
> Everytime I've worked with SQLAlchemy, I've run away screaming in the
> other direction. Sure, portability is a good thing, but at what cost?
I've never found SQLAlchemy to be anything but sane and approachable.
It's really worth understanding _how_ it wor
In article ,
Jabba Laci wrote:
> Hi,
>
> I'm reading the Essential SQLAlchemy book from O'Reilly.
Everytime I've worked with SQLAlchemy, I've run away screaming in the
other direction. Sure, portability is a good thing, but at what cost?
--
http://mail.python.org/mailman/listinfo/python-lis
In Jabba Laci
writes:
> SAWarning: Unicode column received non-unicode default value.
> Column('display_name', Unicode(255), default=''),
Perhaps it would help to supply the default value as a Unicode string
instead of a plain string?
Column('display_name', Unicode(255), default=u''),
--
