On 6/30/07, Brian Beck <[EMAIL PROTECTED]> wrote:
> Last night I put up a TextMate bundle for SQLAlchemy. It has a few
> snippets and templates that should make writing models pretty quick.
> If you've never used TextMate or snippets in TextMate, check out the
> one-minute screencast demonstratin
Hi,
I'm getting this exception: 'Lock wait timeout exceeded; try
restarting transaction".
I've looked through the docs and can't see if there is a way to get SA
to retry itself rather than having to catch this exception and retry.
It would be nicer to have the necessary apparatus to do retries c
Hi Mike,
I've been reading all the changes, it all sounds like a good clean up of
the current SQLAlchemy. I'm not concerned in all the modifications, but
mostly about point #2, assignmapper. Moving everything under query()
really helps against conflicting names that you may give to your class
On Monday 02 July 2007 00:45:18 Eric Ongerth wrote:
> Well, there ought to be more Bravos and Congratulations on this
> thread. I only held back figuring others would pile on well
> enough. Or maybe most of the polymorphists out there are gleefully
> silent about what they're brewing up.
>
> Than
I have a case where SA 0.3.8 create wrong SQL code and an unneeded and
unwanted
INSERT statement. My code inserts a new Arbeitsmittel into the DB using:
Arbeitsmittel = wrapper.getMapper('arbeitsmittel')
d = {'hidx' : hidx,
'zodb_path' : zodb_path,
'versionsnr' : 0,
On Jul 2, 6:37 am, Geoff <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm getting this exception: 'Lock wait timeout exceeded; try
> restarting transaction".
you shouldn't have transactions locking for so long that you're
getting such an error. meaning, try not to have long-running
transactions open.
On Jul 2, 8:39 am, Andreas Jung <[EMAIL PROTECTED]> wrote:
> So why the hell is SA trying to insert something into my 'zielgruppen'
> table?
any table in your SELECT statement for which its full set of primary
key columns are represented in the columns clause of the SELECT, will
generate an INS
Hi! thanks for replying :)
I agree that transactions shouldn't be timing out, the problem happens
when we do a database dump, this locks all the tables for a while and
it happens once a day.
I think I'll go fix it at the source rather than handling it in the
code - i.e. find another way of dumpi
--On 2. Juli 2007 14:22:06 + Michael Bayer <[EMAIL PROTECTED]> wrote:
On Jul 2, 8:39 am, Andreas Jung <[EMAIL PROTECTED]> wrote:
So why the hell is SA trying to insert something into my 'zielgruppen'
table?
any table in your SELECT statement for which its full set of primary
key colu
I would rather ask: How can this behavior be avoided? Is it possible
to mark some columns as read-only/no-write-back?
Best regards
Klaus
On 2 Jul., 16:35, Andreas Jung <[EMAIL PROTECTED]> wrote:
> --On 2. Juli 2007 14:22:06 + Michael Bayer <[EMAIL PROTECTED]> wrote:
>
>
>
> > On Jul 2, 8:
On Jul 2, 2007, at 10:35 AM, Andreas Jung wrote:
>
>
> --On 2. Juli 2007 14:22:06 + Michael Bayer <[EMAIL PROTECTED]>
> wrote:
>
>>
>>
>>
>> On Jul 2, 8:39 am, Andreas Jung <[EMAIL PROTECTED]> wrote:
>>> So why the hell is SA trying to insert something into my
>>> 'zielgruppen'
>>> table
On Jul 2, 2007, at 10:40 AM, klaus wrote:
>
> I would rather ask: How can this behavior be avoided? Is it possible
> to mark some columns as read-only/no-write-back?
>
just remove the primary key columns of the "non-write" tables from
the columns clause of the select.
--~--~-~--
How does one declare Timestamp fields with timezones? The DateTime
maps to TimeStamp without.
Thanks
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalche
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
voltron wrote:
> How does one declare Timestamp fields with timezones? The DateTime
> maps to TimeStamp without.
DateTime(timezone=True)
- --BDS
- --
Benjamin Smedberg
Platform Guru
Mozilla Corporation
[EMAIL PROTECTED]
http://benjamin.smedbergs.u
Thanks!
On Jul 2, 10:14 pm, Benjamin Smedberg <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> voltron wrote:
> > How does one declare Timestamp fields with timezones? The DateTime
> > maps to TimeStamp without.
>
> DateTime(timezone=True)
>
> - --BDS
>
> - --
>
>
I just released SAContext 0.2.1. There are two backward-incompatible
changes due to popular demand:
- sac._session_context is now sac.session_context.
- "dburi" in a Pylons config file is now "uri"; e.g.,
"sqlalchemy.default.uri".
Waldemar Osuch contributed a patch to fix a couple bugs and
Thanks Paul for your answer
but
I was using pymssql.
Now, I am trying to use pyodbc and see if your fix would help... after
struggling to get the URI right on my Linux box, it now simply
crashes ... No error message no nothing, it just dies.
I'll keep looking
Cheers
François,
Paul Jo
Great. This gives us a very good reason to shift everything we have
to Pylons. I like the fact that Pylons gives us that controller as I
think that control is very important in developing a robust
application. I want to know what goes one versus having the framework
do everything for me. Movin
I'm seeing an error with 'autoload' on a simple table. IRC said I
should mention it here, and here it is.
I am running the latest SQLAlchemy 0.3.8 with MySQL-python-1.2.2. This
is running a MySQL database I have no version over. I fear this
version of MySQL is unsupported?
$mysql --version
mysql
19 matches
Mail list logo