Jeremy Dunck wrote:
> On 1/11/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > think adodbapi DOES use parameterization. It's just slightly
> > non-standard. (thus, the %s -> ? stuff above)
>
> I was surprised by this, by the Python DB API allows for parameters in
> the string supplied to the
Cool...thanks! (I have my own, wimpier implementation, so let's see
what I can stea...er, learn from!)
One note: It appears (and you've probably already noticed) that there's
a typo in the Technorati xmlprc ping:
reply = technoratiServer.weblogUpdate.ping('Socialist
Software','http://www.sociali
Yes, we're discussing the SQL migration steps over in dev right now.
Among other things, the change in auth_permission (adding
content_type_id as the referencing field, rather than the reference to
the deleted package field) requires some DML (UPDATEs) to be added to
the migration steps. I'm testi
At this point, the various differences in SQL capabilities between the
backends have resulted in a split of the migration DDL/DML into a
separate list for each engine. I'm working on tweaking them, but I'll
probably get to MySQL last, so feel free to pitch in!
--~--~-~--~~---
You may want to compare those field sizes to a "clean" install of
M-R...if I remember correctly, one or both have been increased in size
in a new install. We'll need to make sure that migrated field sizes
match newly created ones, or we'll end up with WEIRD errors that only
occur with migrated dat
Cool. I'm going the same thing (DDL diffs) tonight or tomorrow with the
SQLite stuff first, and then PosgreSQL. We'll get this knocked out!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To po
I'd say put 'em there!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PR
7 matches
Mail list logo
