Configuration: CentOS 5 (64bit), SA (trunk), Python 2.4.4, py-
MySQLdb-1.2.1, MySQL 5.1-current
Traceback (most recent call last):
File ./indexer.py, line 79, in ?
table[database][conf] = Table(conf, metadata, autoload=True)
File /usr/lib/python2.4/site-packages/sqlalchemy/schema.py,
Dirty fix (works for me):
Index: mysql.py
===
--- mysql.py(revision 2873)
+++ mysql.py(working copy)
@@ -1090,7 +1090,7 @@
table.name = table.name.lower()
table.metadata.tables[table.name]= table
Hi,
SAContext is a SQLAlchemy front end that organizes your engines,
metadatas, and sessions into one convenient object, while still
allowing access to the underlying objects for advanced use.
Mike, this looks like good work and something that is needed. I notice
for instance that the
Hi,
SAContext is strictly a configurational object, it doesnt add any new
I see. I had wondered if this was WSGI middleware that took care of
database transactions (as has been mooted in the TG area recently).
Obviously as a config object, it can't do either of the things I suggested.
I've noticed some large (10x) performance differences between sqlalchemy (no
ORM) and plain DB API when using sqlite and was wondering if that is
something expected even when I'm (trying to) avoid the ORM stuff or if I'm
just doing something wrong.
We have lots of CSV files and I wanted to turn
Well I would prefer not using None and rather making the user pass the
correct key, so that way default become no different they using any other
key and users could just as simply call their key main or what ever else
turns them on. Assuming that they use the correct syntax in the ini file
Hi,
take a look at the current implementation. we are doing this part
already, we're using inspect to look at kwargs. its not fragile at
all. so im just proposing we add extra sniffing of dbapi.connect(),
and that we also look in the query string for the full range of those
On Wednesday 11 July 2007 21:49:48 Mike Orr wrote:
On 7/11/07, Jose Galvez [EMAIL PROTECTED] wrote:
Dear Mike,
I've read the doc string in the new sacontext and was just
wondering why for add_engine_from_config do you have to
explicitly pass None for the default connection? it would make
On Jul 11, 9:02 pm, Justus Pendleton [EMAIL PROTECTED] wrote:
I've noticed some large (10x) performance differences between sqlalchemy (no
ORM) and plain DB API when using sqlite and was wondering if that is
something expected even when I'm (trying to) avoid the ORM stuff or if I'm
just doing
I've just reread the sacontext doc string and realize that what I've said
really does not make any sense. To go back a step I would advocate using
default rather then None
Jose
On 7/11/07, Jose Galvez [EMAIL PROTECTED] wrote:
Well I would prefer not using None and rather making the user pass
Lets say there are Employee, Engineer, Manager, etc whole tree, with
Employee in the root; all levels do have instances and its
polymorphical multitable inheritance.
Let's the Employee has attribute age - number, and manager - pointing
to some other Employee.
how to get all Employees which
On 7/11/07, Mike Orr [EMAIL PROTECTED] wrote:
On 7/11/07, Jose Galvez [EMAIL PROTECTED] wrote:
Dear Mike,
I've read the doc string in the new sacontext and was just wondering why for
add_engine_from_config do you have to explicitly pass None for the default
connection? it would make more
anyway, i copied prop.get_join and removed all polymorphic stuff +
cache, and now such expressions work.
Gaetan, u still interested in this db-cooker of mine?
i think i have something to show...
--~--~-~--~~~---~--~~
You received this message because you are
I've run into this problem as well when working with MySQL 4.0.20c. I
believe the code needs to read:
decode_from = connection.execute(show variables like
'character_set').fetchone()[0]
When issuing that sql at the command prompt, i get back the following:
mysql show variables like
On Jul 11, 2007, at 2:02 PM, Justus Pendleton wrote:
I've noticed some large (10x) performance differences between
sqlalchemy (no
ORM) and plain DB API when using sqlite and was wondering if that is
something expected even when I'm (trying to) avoid the ORM stuff or
if I'm
just doing
On Jul 11, 2007, at 2:49 PM, Mike Orr wrote:
It is awkward but Python has no other built-in value for default.
Using a string means people may spell it differently, and the
.metadata and .engine properties require a fixed value. Making it
optional means the second positional argument
at first glance it seems like you need just session.query
(Employee).join('managers').filter(mgr.c.age 40) ?
oh, but the issue is that managers is self-referring and needs to
be an alias ?
we have a mini feature in 0.4 so far which creates aliases, but its
not quite what you want yet, it
17 matches
Mail list logo
