Hi Paul,
What database connector are you using in your applications that use this
technique?
I use native ODBC running under windows. I wrote a c++ wrapper around
it for
supporting a wide range of dbms with one api in our applications.
Michael
Working with:
SQLAlchemy 0.3.7
Postgresql 8.2
Python 2.4
On my Postgresql 8.2 database server I have a stored function, say
calculateaverage().
When executed from the DBMS software, the stored function updates a
database table.
From my Python script, I am trying to call my stored function like
On May 31, 2007, at 10:29 AM, Alchemist wrote:
No exceptions are raised when this statement is executed. HOWEVER,
the stored function does not seem to perform its required task as the
table that should be updated is not updated when running the script.
the stored procedure must be
just chiming in as a company that is itching pretty hard for this
right
now, our use cases and concerns
yeah...i think most people want to just use bind_to with their
session in order to switch around databases for nowits the most
expedient.
this would solve most of our problems except
Hello list,
I've been having many stability problems with my first SQLAlchemy +
mod_python application. By now I'm thinking it's all my fault and I'm
not using these tools the way they are intended to be used. So I would
like to know how do others organize their code to get something that
the code looks fine. things id make sure of are that youre on 0.3.7
of SA, youre on a very recent version of MySQLDB. also the
use_threadlocal is probably not needed on your engine() and its
worth trying without it since its not as widely tested.
also the common complaint with mod_python
Thanks for the reply Michael,
d make sure of are that youre on 0.3.7
of SA, youre on a very recent version of MySQLDB.
I have SQLAlchemy 0.3.7 and MySQL 5.0.27-standard
he use_threadlocal is probably not needed on your engine() and its
worth trying without it since its not as widely
Roger,
Please excuse the interrupt, but have you applied other fixes? I (and
others) can't event get SQLA to connect to
my Firebird v1.5.4 database running on SUSE Linux.
John
On 30 May, 19:47, Roger Demetrescu [EMAIL PROTECTED]
wrote:
Michael, the patch did the trick...
I was able to
On May 31, 2007, at 3:28 PM, Gambit wrote:
Thanks for the reply Michael,
d make sure of are that youre on 0.3.7
of SA, youre on a very recent version of MySQLDB.
I have SQLAlchemy 0.3.7 and MySQL 5.0.27-standard
more importantly, your mysql-python adapter (MySQLDB). looks like
theyre
firebird is a little like a chicken without a head at this point...im
applying fixes but have no FB database with which to test on.
what results/stack traces/everything else are you getting with the
current SQLAlchemy trunk ?
On May 31, 2007, at 3:33 PM, johnbraduk wrote:
Roger,
Please
Hi John,
I haven't push SA with firebird to the limit, but until now I am happy... :)
And what other fixes are you talking about ? I am using SA 2.7 with
firebird.py modified by changes made in Changeset 2674...
As Michael wrote above, maybe a traceback would help a lot to solve
your
What are future plans for the assign_mapper query methods?
MyClass.select(...)
-- works great. A clear advantage for assign_mapper over the
regular mapper.
MyClass.filter(...)
-- doesn't exist.
MyClass.query().filter(...)
-- works but is undocumented and requires a convoluted
I've been getting this on my Pylons site.
sqlalchemy.exceptions.SQLError: (ReferenceError) weakly-referenced
object no longer exists
It's trying to execute an ORM .select() call. The first time was
after a MySQL server has gone away error, so I assumed some mapped
instances had been orphaned.
On 5/31/07, Mike Orr [EMAIL PROTECTED] wrote:
I've been getting this on my Pylons site.
sqlalchemy.exceptions.SQLError: (ReferenceError) weakly-referenced
object no longer exists
In case it helps, the exception occurs at sqlalchemy/engine/base.py
line 583 (SQLAlchemy 0.3.7):
nothing is weakly referenced within the block where that exception is
being thrown. the only place weakrefs are used outside of the ORM is
a couple of dictionaries in pool.py. you havent said what reproduces
this problem ? you just start the app, and it happens every time ?
On May 31, 6:01
heres the question. Query gets 10 new methods one day. do we then
add 10 methods to assign_mapper() ? must the user class be a total
clone of Query ? assign_mapper just bugs me for this reason. hence
i like entity.query() better. im not sure which one youre saying you
prefer ?
On May 31,
TOFU day? Okay, me too. ;)
If I may cast a vote: yes, please add these 10 methods (if they are
remotely connected to selecting or changing rows) and start with
.filter(). I'm working with assign_mapped objects most the time and just
have to use a completely different (Query) syntax if I want to
It happens only when the site has been idle for several hours; i.e.
overnight. Once it starts it keeps happening every request until I
restart the application.
The first time it happened, somebody had gotten a MySQL server has
gone away error during the night, followed by a couple
maybe keep only _one_ method which gives a fullblown Query() object,
which then can be used as one wish?
On Friday 01 June 2007 06:47:01 Michael Bayer wrote:
heres the question. Query gets 10 new methods one day. do we then
add 10 methods to assign_mapper() ? must the user class be a total
19 matches
Mail list logo
