On 15 Jul 2013, at 18:11, Michael Bayer mike...@zzzcomputing.com wrote:
On Jul 15, 2013, at 11:06 AM, Ed Singleton singleto...@gmail.com wrote:
I have two tables in SQLAlchemy which are identical and I want to update one
from the other where the rows have the same primary key, and I want to
On 19 Jul 2013, at 16:01, Michael Bayer mike...@zzzcomputing.com wrote:
On Jul 19, 2013, at 9:53 AM, Ed Singleton singleto...@gmail.com wrote:
On 15 Jul 2013, at 18:11, Michael Bayer mike...@zzzcomputing.com wrote:
On Jul 15, 2013, at 11:06 AM, Ed Singleton singleto...@gmail.com wrote:
I
On Jul 19, 2013, at 12:14 PM, Ed Singleton singleto...@gmail.com wrote:
A sample script is below (bear in mind that the script contains the two
errors and I wouldn't now expect it to work anyway).
OK this example is calling UPDATE towards email_table as the target, but then
specifies
On Jul 19, 2013, at 9:53 AM, Ed Singleton singleto...@gmail.com wrote:
On 15 Jul 2013, at 18:11, Michael Bayer mike...@zzzcomputing.com wrote:
On Jul 15, 2013, at 11:06 AM, Ed Singleton singleto...@gmail.com wrote:
I have two tables in SQLAlchemy which are identical and I want to update
Thanks, I was just able to test the patch. With the patch, my query with the
extra defer() options added is just a bit faster than without those options. So
while using defer() is not a huge win in my case, it at least no longer causes
an unexpected slowdown.
From: sqlalchemy@googlegroups.com
Thank you for the adice. I see that exclusive relaince on this approach
would prohibit transactions.
The use case at hand is an object storing some information about itself.
As only one object will be saved at a time, I'm thinking this appraoch is
OK. However, I will make the method
Hey gang -
Alembic 0.6.0 has been sitting in the hopper for awhile so I figured I'd put it
out. The two changes here I'm most excited about are no longer needing 2to3
for Python 3, and also I've made the display of history much nicer, since I
used that a lot and I needed something easier
if it's how you want to do it, then go with it for now. If this particular
pattern has trouble in store for you, you'll learn all about that by going
through with it anyway :).
On Jul 19, 2013, at 5:29 PM, Victor Reichert vfr...@gmail.com wrote:
Thank you for the adice. I see that
Sounds great, thanks.
On Wednesday, 17 July 2013 19:35:48 UTC-7, Michael Bayer wrote:
well we try to get releases out every 4-6 weeks but sometimes it takes
longer.though this issue was a surprise and does lean things towards
releasing sooner.
On Jul 17, 2013, at 12:38 PM, Basil
