[sqlalchemy] Re: Cannot abort wxPython thread with SQLAlchemy

2008-06-09 Thread Dominique
Hi Peter, Thank you very much for answering. On 10 juin, 02:38, Peter Hansen <[EMAIL PROTECTED]> wrote: > As Python has no way to actually terminate a thread, can you explain > what you mean by "stop this thread"? Are you simply cloning the code > from the wxPython example, with the delayedresu

[sqlalchemy] Re: Cannot abort wxPython thread with SQLAlchemy

2008-06-09 Thread Peter Hansen
Dominique wrote: > I am using delayedresult (which is a class to do threading in > wxPython) for a query with SQLAlchemy, using SQLite. > > I have an 'opened' session in the main App thread. > > I create another session under the delayedresult thread. > When I try to stop this thread with a dedi

[sqlalchemy] Re: reading from one database and writing to another

2008-06-09 Thread Michael Bayer
On Jun 9, 2008, at 4:57 PM, Jonathan LaCour wrote: > > Michael Bayer wrote: > >>> Thanks I'll take a look. I left out what I think is an >>> important part of this scenario (or maybe it's trivial - I don't >>> have a good perspective on this yet). In any case, I would like >>> to use the ORM c

[sqlalchemy] Re: reading from one database and writing to another

2008-06-09 Thread Jonathan LaCour
Michael Bayer wrote: >> Thanks I'll take a look. I left out what I think is an >> important part of this scenario (or maybe it's trivial - I don't >> have a good perspective on this yet). In any case, I would like >> to use the ORM component of sqlalchemy and completely hide the >> fact that th

[sqlalchemy] Re: sqlalchemy in virtualenv Instructions

2008-06-09 Thread Lukasz Szybalski
On Mon, Apr 14, 2008 at 12:12 PM, Lukasz Szybalski <[EMAIL PROTECTED]> wrote: > On Mon, Apr 14, 2008 at 11:38 AM, jason kirtland <[EMAIL PROTECTED]> wrote: >> >> Lukasz Szybalski wrote: >> > On Mon, Apr 14, 2008 at 11:30 AM, jason kirtland <[EMAIL PROTECTED]> >> wrote: >> >> Lukasz Szybalski

[sqlalchemy] Re: reading from one database and writing to another

2008-06-09 Thread Michael Bayer
we're also assuming that you've exhausted these approaches (which would be a lot more appropriate for this sort of thing): http://forge.mysql.com/wiki/MySQL_Proxy http://dev.mysql.com/doc/refman/5.0/en/replication.html On Jun 9, 2008, at 2:22 PM, qhfgva wrote: > > > > On Jun 6, 12:34 pm, M

[sqlalchemy] Re: reading from one database and writing to another

2008-06-09 Thread Michael Bayer
On Jun 9, 2008, at 2:22 PM, qhfgva wrote: > > Thanks I'll take a look. I left out what I think is an important part > of this scenario (or maybe it's trivial - I don't have a good > perspective on this yet). In any case, I would like to use the ORM > component of sqlalchemy and completely hid

[sqlalchemy] Re: reading from one database and writing to another

2008-06-09 Thread az
u're talking about full replication... what's the possiblity of local-readonly DB to have different (older) data than that of the master? and how this should be tackled? theoreticaly from what i get of the multi-sessions/engine approach, then your two sessions (one writeable:master, one readonl

[sqlalchemy] Re: PostgreSQL and inserting

2008-06-09 Thread Michael Bayer
On Jun 9, 2008, at 12:23 PM, Eric Lemoine wrote: > > Hi. Currently sa does select after insert to get the new serial value? > Is my understanding correct? Thx no, SA executes the sequence corresponding to the integer primary key beforehand. --~--~-~--~~~---~--~--

[sqlalchemy] Re: Ordering null dates

2008-06-09 Thread Michael Bayer
On Jun 9, 2008, at 12:56 PM, Christoph Zwerschke wrote: > > Michael Bayer wrote: >> I tend to use a CASE statement for this: CASE WHEN x IS NULL THEN 0 >> ELSE x . We have case() construct for that. > > Yes, but that still leaves me with having to code "infinity" some way. > >> For your versi

[sqlalchemy] Re: reading from one database and writing to another

2008-06-09 Thread qhfgva
On Jun 6, 12:34 pm, Michael Bayer <[EMAIL PROTECTED]> wrote: > On Jun 6, 2008, at 2:29 PM, qhfgva wrote: > > > > > > > We have (what I think of as) a moderately complicated database > > configuration and I'm hoping there will be a way to configure > > sqlalchemy to deal with it.  The basic scena

[sqlalchemy] Cannot abort wxPython thread with SQLAlchemy

2008-06-09 Thread Dominique
Hello All, I am using delayedresult (which is a class to do threading in wxPython) for a query with SQLAlchemy, using SQLite. I have an 'opened' session in the main App thread. I create another session under the delayedresult thread. When I try to stop this thread with a dedicated button, the t

[sqlalchemy] Re: Ordering null dates

2008-06-09 Thread Christoph Zwerschke
Michael Bayer wrote: > I tend to use a CASE statement for this: CASE WHEN x IS NULL THEN 0 > ELSE x . We have case() construct for that. Yes, but that still leaves me with having to code "infinity" some way. > For your version, use func.coalesce(start, literal_column("timestamp '- > infini

[sqlalchemy] Re: PostgreSQL and inserting

2008-06-09 Thread Eric Lemoine
Hi. Currently sa does select after insert to get the new serial value? Is my understanding correct? Thx 2008/6/7, Michael Bayer <[EMAIL PROTECTED]>: > > > On Jun 6, 2008, at 9:11 PM, Cliff Wells wrote: > >> >> Just an FYI, in PostgreSQL 8.2.4 they added a new feature "returning" >> which can be u

[sqlalchemy] Re: Ordering null dates

2008-06-09 Thread Michael Bayer
On Jun 9, 2008, at 11:34 AM, Christoph Zwerschke wrote: > > I need to order a table by start and end dates, where null values > should > be interpreted as "prior to all values" for start dates and "later > than > all values" for end dates. > > This could be realized with "nulls first", "null

[sqlalchemy] Ordering null dates

2008-06-09 Thread Christoph Zwerschke
I need to order a table by start and end dates, where null values should be interpreted as "prior to all values" for start dates and "later than all values" for end dates. This could be realized with "nulls first", "nulls last", but it seems this did not make it into SQLAlchemy yet (ticket #72

[sqlalchemy] Re: Troublesome relation

2008-06-09 Thread Michael Bayer
On Jun 9, 2008, at 10:50 AM, Paul Johnston wrote: > Hi, > > I have had the following relation working ok for some time, but a > recent update of SQLAlchemy means it's now asking for a remote_side > argument. I'm really not too sure what too put in there - I've never > really understood that

[sqlalchemy] Re: relation metainfo

2008-06-09 Thread Michael Bayer
On Jun 9, 2008, at 1:09 AM, [EMAIL PROTECTED] wrote: > > okay here anopther way to represent it. "this" side is the given > prop/descriptor, and then the hops towards "other" end side: > > MtoN: >containerthis: getattr( prop.parent.class_, prop.key) > midthis: getattr( prop.secondary, pr

[sqlalchemy] Troublesome relation

2008-06-09 Thread Paul Johnston
Hi, I have had the following relation working ok for some time, but a recent update of SQLAlchemy means it's now asking for a remote_side argument. I'm really not too sure what too put in there - I've never really understood that parameter, or foreign_keys. VulnResDesc.mapper.add_property('rawvul

[sqlalchemy] Re: Optimizing a slow query

2008-06-09 Thread EricHolmberg
On Jun 8, 5:09 am, beewee <[EMAIL PROTECTED]> wrote: > Hi, > > thanks for your answers. > > > Other improvements would include (as previously stated by Michael) > > would be to make sure you have indexed all of the items in your WHERE, > > ORDER BY, and ON clauses. > > I created this index: > cr

[sqlalchemy] Re: relation metainfo

2008-06-09 Thread az
okay here anopther way to represent it. "this" side is the given prop/descriptor, and then the hops towards "other" end side: MtoN: containerthis: getattr( prop.parent.class_, prop.key) midthis: getattr( prop.secondary, prop.remote_side[0]) -> this: getattr( prop.parent.class_, p

[sqlalchemy] Re: relation metainfo

2008-06-09 Thread az
On Monday 09 June 2008 03:56:20 Michael Bayer wrote: > On Jun 8, 2008, at 5:02 AM, [EMAIL PROTECTED] wrote: > > hi > > i'm trying to make a metainfo extractor off some relation > > attribute. by metainfo i mean the klas and attr-name of this and > > of the other side of the relation-attribute, or