Oops, sorry about the garbage at the end
On 1/10/07, Rick Morrison [EMAIL PROTECTED] wrote:
A bit of background might be helpful here. The psuedo-sequence mechanism
that the MSSQL modules uses may seem a bit complex, but by leveraging the
same Sequence() mechanism that the PG and Oracle
Michael Bayer wrote:
ok, dont change anything in turbogears yet. i think i have fixed the
problem, please try out rev 2133. ticket #387 explains the issue.
This issue seems very similar to one I found using the MySQL Zope
database adapter. The symptom was the same (MySQL has gone away), and
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
I myself don't need it, but Paul, if you want to take a swag at it, I'll be
happy to review any patch.
Rick
On 1/10/07, Michael Bayer [EMAIL PROTECTED] wrote:
the Column has the autoincrement=True flag on it, and you can detect
that its a PRIMARY KEY column + Integer. if MS-SQL dialect
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
it should be pretty stable, we havent had much dramatic going on. i
moved some things around a bit in r2174 with regards to eager loading
but i think those changes have ironed out pretty well.
On Jan 10, 2007, at 10:39 PM, Daniel Miller wrote:
Hi Mike,
I've been lurking here in the
On 9 Jan., 22:59, Jonathan Ellis [EMAIL PROTECTED] wrote:
You're trying to dynamically add columns to the table in the database,
or just to the Table instance?
Just to the Table instance, no database tables should exist at that
point.
--~--~-~--~~~---~--~~
