[sqlalchemy] sqlalchemy.org down?

I can't reach www.sqlalchemy.org, anyone else having problems? Arnar --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe

[sqlalchemy] Re: Latests unicode changes breaking MSSQL

Theres a hook I added for supports_unicode_statements() on Dialect that will tell the engine to stringify the queries before being sent.Oracle implements one that returns False, for example. just add one in and have it return false. but, I thought MS-SQL supports unicode column names

[sqlalchemy] Re: sqlalchemy.org down?

On 3/29/07, Michael Bayer [EMAIL PROTECTED] wrote: rebooting hopefully it comes up Works for me, thanks. Arnar --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send

[sqlalchemy] Re: Connection handling, re-establishing connections?

On 3/25/07, Michael Bayer [EMAIL PROTECTED] wrote: Still, all of these measures require that we actually get an error thrown to detect that a restart took place, which inconveniently usually happens not at the point of cursor() but at the point of execute(), and we dont have any frameworks in

[sqlalchemy] Sqlalchemy with ORM difficulties

Guys, I am having some difficulties in the following code. I skipped a few lines but basically I think the logic is very clear. In the line u.save() it produce the error which is pasted in part 2. I found that the self object under save method is different than the original one that i created by

[sqlalchemy] Re: Sqlalchemy with ORM difficulties

save() should not be a @classmethod. also consider using the assignmapper extension which I think accomplishes what youre looking for. On Mar 29, 2007, at 2:35 PM, Riddler wrote: Guys, I am having some difficulties in the following code. I skipped a few lines but basically I think the

[sqlalchemy] before_insert in mapper extension

If a mapper extension modifies an attribute of an instance (the same instance being saved) in a before_insert() or before_update() call, are those attributes tracked as changed so they'll be included in the update? If not, is there any way to mark those items as changed? Thanks, Rick

[sqlalchemy] Re: before_insert in mapper extension

theyre tracked as changed but the unit of work has already figured out the full list of elements it wants to save (remember that it has alraedy built up the full order of operations using a dependency sort). if you want to affect the list of elements to be saved you might want to do that

[sqlalchemy] Re: before_insert in mapper extension

On Mar 29, 2007, at 5:43 PM, Rick Morrison wrote: Thanks. Does that full list of elements include individual instance attributes or just instances? we're talking about session.dirty and stuff like that, its instances. What happens if the before_update of an instance, the handler