Mike Bernson wrote:
I have attached the code doing the write to the database
and a traceback with local variable being display for
each frame.
I am also attaching a run with nothing catching the error
so you can see the simple traceback with the exception.
Here is output from mysql show
Jorge Vargas wrote:
Hi,
I'm working on a project where I got several read only tables that
are dependent on a third-party, I got several vainlla SQL queries to
get the data I need of them and I was wondering which will be the best
way to load them up into SA. The queries themselfs are
Michael Bayer wrote:
so, does somebody want to add EXEC to the is_select() regexp ?
I think we should also add a flag to text() which allows this too,
along the lines of returns_results=True.
There was some talk of trying to auto-detect resultsets with cursor
inspection. My recollection
Rick Morrison wrote:
This approach would be ideal, and would work with row-returning
functions, etc. but obviously depends on some rather sophisticated
cooperation with the dbapi. I don't think pymssql would be up to the
task, although I think the ODBC-derived dbapis might work.
It's not
Felix Schwarz wrote:
Thank you very much for your reply - lightning fast as always :-)
Gaetan de Menten schrieb:
Other than that, maybe you are (or Turbogears is)
starting a transaction somewhere (with session.begin()) without ever
commiting it?
Thanks for your hint. Indeed I used
Cliff Wells wrote:
This appears to be a bug in SA 0.4.2p3:
From the datetime docs:
'''
Note: In order to stop comparison from falling back to the default
scheme of comparing object addresses, datetime comparison normally
raises TypeError if the other comparand isn't also a datetime
On 0.3.x, use EXT_PASS rather than EXT_CONTINUE.
Michael Bayer wrote:
sorry, the docstring is wrong. create_instance() should return
EXT_CONTINUE if it would like to bypass creating the instance itself.
However, self here is the MapperExtension instance, not the mapped
instance.
Max Ischenko wrote:
Hello,
I'm struggling with a simple one to many relation, pls help!
active_meetup = MeetupEvent(...)
reg = MeetupRegistration(meeting=active_meetup)
db.save(reg)
*class 'sqlalchemy.exceptions.OperationalError': (OperationalError)
(1048, Column 'meeting_id'
Steve Zatz wrote:
I realize this is actually an SQL question but I haven't been able to
figure out the answer.
In a simple self-referential table, the following produces all the
Nodes that are parents to some child node(s):
node_table_alias = node_table.alias()
parents =
Manlio Perillo wrote:
Michael Bayer ha scritto:
On Jan 28, 2008, at 6:03 AM, Manlio Perillo wrote:
Hi.
In this wiki page:
http://www.sqlite.org/cvstrac/wiki?p=ForeignKeyTriggers
there is a recipe on how to add basic foreign key support to SQLite
using triggers.
Is it possible to
Nick Joyce wrote:
Hi,
I am developing a web app using SQLite (which I will switch to
PostgreSQL in production) and came across a weird select error when
using schema. The attached file test.py reproduces the error and
output.txt is the output from running the script.
I have tested
Adrian wrote:
I am trying to change the default column type mapping in sqlalchemy.
Analogous to the description in the MySQLdb User's Guide (http://mysql-
python.sourceforge.net/MySQLdb.html) I tried the following.
from MySQLdb.constants import FIELD_TYPE
my_conv = { FIELD_TYPE.DECIMAL:
Kumar McMillan wrote:
Hello, I have not been able to figure this out from the docs.
I would like to setup and teardown test data using mapped classes.
The problem is that those same mapped classes need to be used by the
application under test and in case there is an error, the teardown
Frank Wierzbicki wrote:
On Jan 17, 2008 4:35 PM, jason kirtland [EMAIL PROTECTED] wrote:
I've got a local branch going to formalize the multi-driver support
ease using SQLAlchemy on alternate VMs. Adding ODBC to a single-driver
dialect in CPython was my step 1, next up is sqlite via JDBC
Frank Wierzbicki wrote:
On Jan 19, 2008 1:00 PM, jason kirtland [EMAIL PROTECTED] wrote:
Frank Wierzbicki wrote:
I'm not too far yet with Jython- still working on CPython issues. This
weekend I plan to check in a tool that converts the test suite source
into 2.3-compatible syntax, enabling
Christophe Alexandre wrote:
Dear All,
Send me some study material on DBMS + $100 !
Or if it fits you better, can you please help on the issue described
below?
The closest situation to what I am facing is described here:
Rick Morrison wrote:
Adodbapi is Windows-only, you're definitely barking up the wrong tree
with that one.
Pyodbc on Linux is theoretically possible, but I know of no users and
have very little experience myself with it.
Pymssql is supported on Linux, and it works within certain
Rick Morrison wrote:
I'm having trouble with the instrumented lists used for relation
collections:
def setProp(self, new_prop, exclusive=True):
self.props = [p for p if p.typ != new_prop.typ]
self.props.append(new_prop)
so if 'props' is a relation on some mapped class, and I
Rick Morrison wrote:
def setProp(self, new_prop, exclusive=True):
if exclusive:
self.props = [p for p if p.typ != new_prop.typ]
self.props.append(new_prop)
o = MappedObject()
o.setProp(Prop(typ='a', val='b')
o.setProp(Prop(typ='b', val='c')
MappedObject has a simple
Rick Morrison wrote:
On Jan 17, 2008 7:32 PM, jason kirtland [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Rick Morrison wrote:
def setProp(self, new_prop, exclusive=True):
if exclusive:
self.props = [p for p if p.typ != new_prop.typ
Jaimy Azle wrote:
Hi,
I have a problem on using Decimal type along with SQLAlchemy, the
decimal value could not be used for any computation after querying
something with SQLAlchemy object. This is reproducable in my machine:
import decimal
from tbl import SBCITM
pval =
phasma wrote:
What character set is the db-api driver using? Try:
engine.connect().connection.character_set_name()
If it's not utf8, you can configure the driver by adding 'charset=utf8'
to your database url.
I add charset='utf-8' to 'create_engine' function, but before send
Alexandre da Silva wrote:
Hello all,
is there a way that I can get the default value defined on
Column(default=something) ?
the default I get is a ColumDefault, and I don't know how to get it's
value.
any suggestion?
The value is in its .arg property: col.default.arg
Mike Bernson wrote:
Database is mysql
I am having a problem with unicode and binary type.
I am using an XML parse the return Unicode strings.
I have a table in mysql with the default character set as utf8
I set the charset to utf8 in the connect string to charset=utf8
I am trying
Smythe wrote:
On Jan 8, 12:25 am, Michael Bayer [EMAIL PROTECTED] wrote:
passivedefaults are reflected in 0.4 just as they are in 0.3, as much
as the underlying database allows them to be discovered.
Thanks for the quick reply. I reduced this to a small example and it
seems the failure
phasma wrote:
Hi!
I'm using mysql
*** 1. row ***
Variable_name: character_set_client
Value: utf8
*** 2. row ***
Variable_name: character_set_connection
Value: utf8
Lele Gaifax wrote:
Hi all,
I was finally able to spend a little time on the Firebird backend, and
I'm glad to say that I'm currently down to this test summary:
[...]
C. a few tests don't use an explicit ordering, and assume that the
result of a select without an ORDER BY matches the
King Simon-NFHD78 wrote:
Hi,
I'm connecting to an ancient version of MySQL (3.23.58) that (as far as
I can tell) doesn't support basic JOIN table ON condition syntax
Ie. this gives a syntax error:
SELECT * FROM productversions pv
JOIN producttypes pt ON pv.producttype =
King Simon-NFHD78 wrote:
Jason kirtland wrote:
King Simon-NFHD78 wrote:
Hi,
I'm connecting to an ancient version of MySQL (3.23.58)
that (as far as
I can tell) doesn't support basic JOIN table ON
condition syntax
This is in r3916. It's a simple change that can be easily monkey
Expo wrote:
I'am using SA 0.3.11 with MySql 5.0 through MySQLdb latest stable
version and I don't get results when searching string with chars acute
or grave like è, é, à.
I haven't found flags on SA or MySQLdb for support exotic chars, I
have miss something ?
There is an option to MySQLdb
david wrote:
Hi Jason -
Thanks a lot for the test. It is very helpful.
However, when I try running it on the mysql-5.0.38 machine as a
starting point for testing, (with appropriate mods for version, etc),
I get very mixed results. There are 6 cases in your test:
1. use_unicode=1,
david wrote:
Hi,
I can see that this has been discussed before, but I am totally
baffled as to what is happening.
I.
ubuntu
mysql version 5.0.38
with :
MySQL_python-1.2.2
SQLAlchemy-03.10
python-2.5
Using SA, I can insert and select unicode data with no problem. All
the mysql
fw wrote:
Hi,
I am having a weird problem. I am dealing with some legacy database,
so I subclass TypeDecorator to help clean things up a bit.
This worked fine in 0.3 but I am now trying to use 0.4 and things
break in the strangest of way.
When I run the file below, Python complains
bob wrote:
Hi,
I am going over this this example to learn how to construct an eager-
loaded adjacency tree,
http://www.sqlalchemy.org/trac/browser/sqlalchemy/trunk/examples/adjacencytree/byroot_tree.py
and I noticed that some of the keys in the treenodes table are given
long names in
Bruza wrote:
By using %s, does that mean MySQL does not support binding of
parameter
and will have to pass the entire SQL statement as one text string?
c.execute(select * from t_test where c1=%s % '1234567')
That should be a comma separating the bind values, not a % format operator:
Michael Bayer wrote:
On Nov 7, 2007, at 6:01 AM, klaus wrote:
This is strange. I had problems reproducing the bug for a long time
and was now quite happy that I succeeded.
Yes, I'm using PostgreSQL 8.1.5 and psycopg2. And I still see the
behavior that I reported. That should narrow the
Michael Bayer wrote:
what happens if you change the create_engine to:
engine = create_engine('sqlite://', echo=True, paramstyle=named)
that doesnt reproduce for me on linux. i find it hard to believe its
a bug within the PG dialect itselfbuilding PG on my linux box now.
No
Paul Johnston wrote:
I have just put a proposed patch on ticket #573. It uses info as the
name and puts it on SchemaItem. Due to the way constructors are arranged
for SchemaItem subclasses, I've explicitly put this in the constructor
for Table and Column.
Happy to take further comments
Rick Morrison wrote:
On 10/26/07, *Paul Johnston* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Ticket #573 mentions adding a field for arbitrary
application-specific information to tables. I now have a need for
this, so I'm prepared to do the work to make it happen.
Rick Morrison wrote:
personal opinion: I'm not wild about either 'attributes' or 'properties',
(a) they seem too long, and
(b) yes, they are too similar to generic ORM terms
many many moons ago (pre Windows-1.0 ) I used an Ascii-GUI thing called
C-scape (I think it's called vermont
Rick Morrison wrote:
The core can (and does) use these buckets too, so I'm not sure
about the
user-y moniker.
Hold it. I thought the whole point of this was to separate core usage
from user usage? To create a safe-zone for library user's private data.
Yes to the second
Lukasz Szybalski wrote:
On 10/23/07, Marco Mariani [EMAIL PROTECTED] wrote:
Lukasz Szybalski wrote:
dev.cfg has
sqlalchemy.dburi=mysql://user:[EMAIL PROTECTED]:3306/dbname
I did this in dev.cfg :
sqlalchemy.convert_unicode = True
sqlalchemy.dburi=mysql://user:[EMAIL
Travis Kriplean wrote:
Hello,
We're running into a problem with case in the reflected column names
between mac and windows both using sqlalchemy 0.4.0. For example, in
our mysql database, we have a table with columns named END_YEAR and
DESCRIPTION. On a windows box:
print table.c
Jim Musil wrote:
I don't see support for RLIKE, NOT RLIKE, or REGEXP anywhere.
Is there support for this?
Yes, you can use these operators and any others via the .op() method:
table.c.col1.op('rlike')('re')
not_(table.c.col1.op('rlike')('re'))
table.c.col1.op('regexp')('re')
-j
Noufal wrote:
Hello everyone,
I'm having some trouble with a query involving a timedelta
object with a mySQL backend (MyISAM). I have a table called Run
that has two fields like so.
sa.Column('starttime', sa.TIMESTAMP),
sa.Column('endtime', sa.TIMESTAMP)
I'm trying to find all
Noufal wrote:
On Sep 20, 10:34 pm, Noufal [EMAIL PROTECTED] wrote:
[..]
I create the tables using SQLAlchemy. I'll send you the output in a
day, I'm away from the machine where this code is right now.
The output of the create table column looks like this
CREATE TABLE `stats` (
`sid`
Noufal wrote:
Hello everyone,
I've recently picked up SQLAlchemy for a project that I'm working
on. I couldn't get a version newer than 0.3.10 (admin bureaucracy) and
have to use this.
I create two tables like so
run_table = sa.Table('runs',md,
Rick Morrison wrote:
This is Python, after all, and it would be trivial to simply put
whatever attribute you want on a Table, Column or any SA object.
SA would just need to stay out of the way and agree not to use a certain
attribute like description or userdata, or whatever.
There is a
Felix Schwarz wrote:
Hi,
I have a question related to sql injection when using a clause like
this: User.c.username.like('%' + userinput + '%')
What restrictions do I have to put on the variable userinput? Of course,
I will ensure that is no percent character ('%') in userinput. Is that
King Simon-NFHD78 wrote:
Hi,
The ancient version of MySQL that I am connecting to (3.23.58) doesn't
support the syntax 'LIMIT limit OFFSET offset' syntax. Instead, it
uses LIMIT offset, limit. This is described in the docs, but it
doesn't say what version introduced the more standard
sc0ttbeardsley wrote:
On Sep 17, 5:03 am, [EMAIL PROTECTED] wrote:
Has anyone added support for the POLYGON data type in PostgreSQL? If
so, is there any code that can be shared?
I haven't seen POLYGON but the beginnings of such support is over at
bycycle.org[1]. I'm interested in something
jean-marc pouchoulon wrote:
helo,
I don't understand why my sqlite database is locked on a drop ( the code
is following)
thanks for your explanation.
[...snip...]
ordinateurs = computers_table.select(computers_table.c.prix
100.0).execute()
ordinateur_pas_cher =
Anil wrote:
On Sep 14, 7:36 am, Anil [EMAIL PROTECTED] wrote:
class 'sqlalchemy.exceptions.FlushError': instance Location is an
unsaved, pending instance and is an orphan (is not attached to any
parent 'Host' instance via that classes' 'location' attribute, nor any
parent 'User' instance via
Hermann Himmelbauer wrote:
Hi,
In one of my database tables I have a varchar that is mapped to an object
with
a string attribute. This specific varchar should however be represented by a
certain Python object, therefore it would be very handy, if there would be a
way to automatically
ANSI defines the SQLSTATE error codes for portable errors. I think
there is SQLSTATE support in most of the databases SQLAlchemy supports
(but none in SQLite that I can find), and the error code should be
available via db-api either directly (pyscopg2, mysql-python, at
minimum) or can parsed
Jean-Philippe Dutreve wrote:
Thanks Jason for your clear explanation.
Is there any mean to do your suggestion to call the pure Python
version without coping/pasting it into my module?
Not that I know of- the Python functions get overwritten by the C
implementations when the module is
Jean-Philippe Dutreve wrote:
I was using SA 0.3.9 to insert an item in an ordered list with bisect
method insort (py 2.5):
mapper(Entry, table_entries)
mapper(Account, table_accounts, properties = dict(
entries = relation(Entry, lazy=True,
backref=backref('account',
remi jolin wrote:
Hello,
I have the following definition (using Elixir)
class Manifestation(Entity):
has_field('price', Numeric)
The DB is mysql
and something like
m = Manifestation(price=10.0)
then when accessing to this manifestation again (after flush, clear, etc...)
I have
remi jolin wrote:
le 07.09.2007 19:47 remi jolin a écrit:
le 07.09.2007 19:27 Michael Bayer a écrit:
numeric types are going to come out using decimal.Decimal objects in
0.4 but not exactly sure whats happening there...do a repr(m.price).
it gives Decimal(10.00)
and I'm
Marcin wrote:
Seems he already did this ;-) And he also improved my patch, in
the meantime I discovered that while my patch was sufficient to
avoid the failure, internally enum values were not correctly
extracted (noticed this while inspecting in the debugger, not
sure whether it is of any
Some other postgres-friendly options from the IRC channel:
select([func.date(model.channel_events.c.stamp)], distinct=True)
or
select([cast(model.channel_events.c.stamp, Date)], distinct=True)
The latter should be portable anywhere, I think. Not sure about
the first beyond the 3 usual open
Marcin Kasperski wrote:
Attached patch seems to resolve both problems.
Thanks, this is fixed in r3464.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to
Orest Kozyar wrote:
class user(object):
__metaclass__ = EntitySingleton
def __init__(self, firstname, lastname):
pass
class pet(object):
__metaclass__ = EntitySingleton
def __init__(self, owner, species):
pass
I changed __call__
voltron wrote:
Hi all
What do I have to import to be able to use the column type TEXT?
from sqlalchemy import Column, TEXT
Column('mytext', TEXT)
or use 'String' without a length qualifier:
from sqlalchemy import Column, String
Column('mytext', String)
Jian wrote:
Hi List:
I am just doing a test of my pylons site under medium load.
(ab2 -c 20 -n 5000 ...)
and got following errors:
2007-08-29 17:32:34,468 INFO [paste.httpserver.ThreadPool]
kill_hung_threads status: 10 threads (10 working, 0 idle, 0
starting) ave time 2.24sec, max
Jian wrote:
Hi Jason,
thanks for the reply.
My pylons basecontroller takes care of the session clean up
like this:
class BaseController(WSGIController):
def __call__(self, environ, start_response):
try:
return WSGIController.__call__(self, environ,
Jian wrote:
the remove is described in doc as close + extra cleanup
Shouldn't the doc be updated to add that point, which will make
the the life of newbies like me easier =D
Or better: add the explicitly close in remove.
Yeah, the current remove() implementation in trunk isn't yet in
sync
Mike Bernson wrote:
Using SQLAlchemy version 0.4b4. When reflecting
table from mysql database with tinyint(1) you get
a boolean back. I think this is error because it
returns a bad data type for tinyint(1).
I have a database that work under 0.3.0 where to
store a single digit I used
pablo wrote:
Sorry, but I'm still having the same issue. I updated only the
file in the changeset and the error keeps appearing. I'm missing
something?
That table is reflecting without issues for me in the trunk. Are
you seeing the same warning in the log?
Mike wrote:
I'm upgrading a Pylons app from SQLAlchemy 0.3 to 0.4. One table
is defined as:
incidents = Table(IN_Incident, meta,
Column(orr_id, Integer, primary_key=True),
autoload=True, autoload_with=engine)
The table is a MySQL VIEW that contains a column 'is_top'.
MySQL
Hi Anil,
The recent 0.4 betas have an all-new MySQL table reflection routine
that's being tried out. It's possible that it's not picking up
your primary key when it should- could you send in the output of
SHOW CREATE TABLE for this table, either on or off list? Also
there should be a
Anil wrote:
Actually, there was some information in the logs that I just noticed
that might help detect the problem (some kind of unicode issue?):
12:58:21,710 INFO [sqlalchemy.engine.base.Engine.0x..50] SHOW CREATE
TABLE `User`
12:58:21,711 INFO [sqlalchemy.engine.base.Engine.0x..50]
svilen wrote:
a suggestion about _list_decorators() and similar.
they can be easily made into classes, i.e. non dynamic (and
overloadable/patchable :-).
The stdlib decorators end up in a static, module-level dictionary that
can be manipulated if you want to. Wouldn't this be replacing a
svilen wrote:
And anyway i need to first create the object and just then append it
(the decorators will first fire event on the object and just then
append(), that is call me), so may have to look further/deeper.
Maybe i can make my append create objects first and then call the
actual
Arun wrote:
So in short if I specify use_unicode=True at the SA engine level
then I can skip specifying use_unicode and specify only
charset=utf8 at mysqldb level ?
If you configure this DB-API driver for all-Unicode (which is what
happens when you only give it a 'charset') all strings will
[EMAIL PROTECTED] wrote:
On Monday 20 August 2007 18:09:41 jason kirtland wrote:
svilen wrote:
And anyway i need to first create the object and just then
append it (the decorators will first fire event on the object
and just then append(), that is call me), so may have to look
further
Arun Kumar PG wrote:
Ok, you need to get that charset to the driver. Try removing SET
NAMES from your init_command, and instead pass charset=utf8 and
use_unicode=0 in your database connection URL.
why do we want to say use_unicode=0 instead or use_unicode=True here?
You can
Arun Kumar PG wrote:
Hi All,
Recently I upgraded to the version 3.9 of SA. Post that whenever I am
trying to save characters in different language in the table I am
getting the below exception:
File /src/sqlalchemy/engine/base.py,
line 601, in _execute
raise
Arun Kumar PG wrote:
All tables are having a charset of utf8. Additionally, I am issuing SET
NAMES 'utf8' statement as a part of connection establishment.
Anything that is wrong here or missing ?
Are you updating the connection character set in the driver as well
after issuing SET NAMES?
am
issuing SET NAMES 'utf8' statement as a part of connection
establishment.
Anything that is wrong here or missing ?
On 8/15/07, jason kirtland [EMAIL PROTECTED] wrote:
Arun Kumar PG wrote:
Hi All,
Recently I upgraded to the version 3.9 of SA. Post that whenever
I am trying to save
Ok you need to get tArun wrote:
I am using mysqldb-1.2.2. I am passing 'SET NAMES' to connect
method as a value for init_command parameter. All tables have
utf8 charset. And I pass convert_unicode=True to engine.
Let me know if anything else is required.
Ok, you need to get that charset to
Martin Aspeli wrote:
Hi all,
I have a use case where I need to execute a MySQL LOAD DATA INFILE
statement on an SQLAlchemy connection.
I've tried this is with an engine using a threadlocal strategy, using
engine.scalar() and passing a string that contains the (generated)
LOAD
DATA
hiroshiykw wrote:
Hi.
In SQLAlchemy 0.3.10 ( / Python2.5), I found that YEAR column
type is created as TEXT column type in the following
[...]
Sorry about that. This is now fixed in the trunk for 0.4 and in
the 0.3 maintenance branch.
Cheers,
Jason
Boris Duek wrote:
2. I was assigning Python-bool value (True,False) to a TINYINT(1)
column.
But No 2. - maybe sqlalchemy could know that True is 1 and False is
0 because MySQL (the database to which I connect) treats its own
BOOL type as an alias to TINYINT(1)?
The Boolean column type
Michael Bayer wrote:
On Jul 30, 2007, at 4:58 PM, Jonathan LaCour wrote:
Michael Bayer wrote:
its a model taken from the way event loops usually work; any consumer
along the event chain is allowed to say, ive consumed the event and
stop further handlers from dealing with it. we can
Arun Kumar PG wrote:
Looks like the problem is coming because of the fact when we are
updating a row in table with the same data the rowcount returned by
mysql is 0. Only when there is a change in data the rowcount is returned.
Are you creating connections outside of SQLAlchemy? (I seem to
Marco wrote:
svilen ha scritto:
Anyway it may depend which audience are u targeting with these
names - those who never seen an API or those for which names
are important only to associate them with a
library/version/use-case... both extremes are equaly
uninteresting imo.
I think
With 0.4 almost upon us, we're coming down to the wire for big changes
getting in- and some things are kind of now or never.
I've found myself explaining engines and metadata with some particular
language lately, and I wondered, what would it look like to just put
that terminology in the names
Mike wrote:
sounds good. Looking forward to see it in 3.10dev
The case-check cache in the trunk and will be in the forthcoming
0.3.10.
Since it's a connection-scoped cache, you'll want to re-use the
same connection for all of the table autoloads you're doing. If
you're autoloading at the
Mike wrote:
I started looking to what is happen to get table information from
mysql.
I found that the following is issued for every table that is
reflected:
2007-07-18 00:29:08,158 INFO sqlalchemy.engine.base.Engine.0x..cc
show variables like 'character_set%%'
2007-07-18 00:29:08,158
[this one seems to have been lost in googlegroups too, resending...]
Mike wrote:
I started looking to what is happen to get table information from
mysql.
I found that the following is issued for every table that is
reflected:
2007-07-18 00:29:08,158 INFO
Mike wrote:
can it also be added to 3.9 ?
Sure, if there's another release in the 0.3 line the case-check
cache can go in. But the only use SHOW CREATE change will be
likely be a 0.4-only thing.
-j
--~--~-~--~~~---~--~~
You received this message because
SamDonaldson wrote:
[...]
I have defined a transaction decorator:
def transaction(func):
def do(*args, **kw):
connection = engine.connect()
transaction = connection.begin()
try:
# create some context here for the connection and pass it
through to
I've made changes in the trunk for 0.3.9 that I hope will take care
of reflection issues reported in MySQL 3.23, 4.0 and 4.1, as well
as odds and ends in current releases. It would be super super
useful if anyone who has had reflection issues in the past to pull
a copy of the trunk and give
bbull wrote:
I just tested this on MySQL 4.0.20c and it seems to have solved
the autoload problem.
Great. Thank you!
What is the timeframe for cutting the 0.3.9 release?
Very soon, probably in the next couple of days.
-j
--~--~-~--~~~---~--~~
You
Ron wrote:
Ok, I applied that change to the version I'm using (0.3.8). That
fixed it.
But I think I stumbled on another bug/inconcistancy.
If I tried to str/repr obj.attr it failed.
[...]
Does that make sense? Or is the problem deeper in the code? It
seems to go along with what you
Ron wrote:
Now I'm having trouble with updating values in AttributeDict:
so
obj.attrs['key'] = 'somevalue' (works)
obj.attrs['key'] = 'newvalue'(second one doesn't work)
I get this error:
File /usr/local/lib/python2.4/site-packages/SQLAlchemy-0.3.8-
Ron wrote:
When I try the above I get this error at flush time:
InvalidRequestError: Class 'str' entity name 'None' has no mapper
associated with it
Here is my dictionary collection_class:
class AttributeDictNEW(dict):
My Attribute Dict
def append(self, item):
FYI the MySQLdb 1.2.1 gammas 1 through 3 seem to have this blob
issue. 1.2.1 and 1.2.2 final are both OK.
Mike wrote:
will try one a few systems and different MYSQLdb
The mysqlDB 1.2.1gamma3
__author__ = Andy Dustman [EMAIL PROTECTED]
__revision__ = $Revision: 1.36.2.4 $[11:-2]
Michael wrote:
attached is an approach that uses just the tiniest amount of
awareness of how a mapper works, to do the whole optimized
loading scenario ahead of time, and you get an object with your
two distinct pro and con relationships, no list decoration
or anything needed. the
101 - 200 of 200 matches
Mail list logo
