Hi Mike, I've been lurking here in the shadows for a while...this particular topic looks very interesting to me and I'd love to upgrade to HEAD to try it out. However, I'm wondering what the risk factor is in doing that? Have there been any other major (potentially destabilizing) changes lately? I'm using r2168 right now, and it's been very stable. I've upgraded to HEAD quite a few times over the past year and I've always been impressed with (1) the overall stability of SA and (2) speed with which bugs were fixed when they are found. I'm just asking for a general idea of how stable you feel the trunk is right now. Don't worry, I'll take responsibility for my actions and will in no way hold you responsible for anything that may occur if I decide to upgrade right now--just looking for a general indicator. Thanks.
~ Daniel Michael Bayer wrote: > server-side cursors (i.e. named) for all postgres functionality by > default is currently in the trunk, and you can turn it off by saying > "client_side_cursors=True" in create_engine(). however one user > reported that table reflection breaks, which I cannot reproduce. so > can some folks please try out the trunk with postgres and see if we can > go with server side cursors by default? ive run the unit tests many > times with both settings and i dont perceieve any performance hit from > using server side cursors. id like this to be in the next release, but > if theres some issue using server side cursors in all cases, then i > have to break open the code and make it a lot more complex to detect > the conditions where server-side cursors are appropriate. > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
