I mean non-ascii column names defined in my database table.
SqlServer, Oracle, MySql...all of the mainstream DBMS support this
feature,
In east asia(China, Japan, Korea), non-ascii column names and table
names,together with non-ascii strings in record
are widely used.
On 3月25日, 下午10时55分, Michael
Ok I saw fixes in the current trunk:
class MSSQLDialect_pymssql(MSSQLDialect):
def make_connect_string(self, keys):
if keys.get('port'):
# pymssql expects port as host:port, not a separate arg
keys['host'] = ''.join([keys.get('host', ''), ':',
dialects can be used on their own without the engine being present
(such as, to generate SQL), also you can construct an engine passing
in your own module object which might have been procured from
somewhere else (or could be a mock object,for example).
On Mar 26, 2007, at 11:45 PM, Monty
On Mar 27, 2007, at 2:08 AM, chris e wrote:
specific to the identity of the object. Is there currently a way, or a
plan to support, splitting the polymorphic query into two queries? The
first would get the base table, the second would retrieve the details
based on the discovered table.
didnt get your attachment. but yes, they are different. during a
many-to-many flush() operation, the two relationships know to
communicate which one actually dealt with the row in the many-to-many
table, without it, youll get duplicate association rows.
additionally, the automatic
I upgraded to 0.3.6 from 0.3.5 and one of my querys stopped working:
s =
model_table.select(~(model_table.c.therapeutic_area.in_('Respiratory','Diabetes',
'Inflammation','CVD')),
order_by=[model_table.c.model_acronym])
All my other query still work fine.
On Mar 27, 2007, at 10:00 AM, Julien Cigar wrote:
Hello,
I'm using SQLAlchemy 0.3.5, and it seems that the func() output is
broken with some functions.
I use the ANY function of PostgreSQL with something like :
func.any(q.c.habitats)==filter_habitat
SQLAlchemy translates this in:
On Tuesday 27 March 2007 17:18:04 Michael Bayer wrote:
On Mar 27, 2007, at 3:53 AM, [EMAIL PROTECTED] wrote:
Lets say u have 5 leaf types in 4-5 levels of the hierarchy tree,
say that makes 10 tables total.
say E object is a leaf and comes from A.join(B).join(C).join(E) -
so E is split
Here is the surrounding code:
def model_list(therapeutic_area='All'):
if therapeutic_area == 'All':
s = model_table.select(order_by=[model_table.c.model_acronym])
elif therapeutic_area == 'Other':
s =
But following the second post (see below), I have read the
documentation,
though not very carefully, and have not validated it by test code,
but the documentation really shows the solution to my problem.
Have I misunderstood the documentation?
--
second post
On 3/27/07, Michael Bayer [EMAIL PROTECTED] wrote:
didnt get your attachment.
Yeah, I forgot it, as usual, but it wasn't very import anyway...
but yes, they are different. during a
many-to-many flush() operation, the two relationships know to
communicate which one actually dealt with the
from the docstring in
class Column:
def __init__()
name
The name of this column. This should be the identical name as it
appears, or will appear, in the database.
key
Defaults to None: an optional alias name for this column. The
column will then be identified everywhere
On Tuesday 27 March 2007 18:12:37 Chen Houwu wrote:
from the docstring in
class Column:
def __init__()
name
The name of this column. This should be the identical name as
it appears, or will appear, in the database.
key
Defaults to None: an optional alias name
I am doing some experimenting with this, and it would appear that
Psycopg2 (not sure about postgres itself) can not handle unicode
column names. sqlite and mysql adapters do handle unicode table and
column names.
so in changeset 2447, I have made some adjustments so that unicode
table
this is most likely a typing error and id need to see the types of
columns being used. in particular if you have any String columns
without a size, they are now interpreted as CLOBs which might be
where its tripping up.
On Mar 27, 2007, at 10:35 AM, shday wrote:
Here is the surrounding
Hi,
The table is reflected, with one column overridden, here:
model_table = Table('model',metadata,
Column('model_id',Numeric(precision=6,length=0),Sequence('model_seq'),
primary_key=True, nullable=False),
autoload=True)
Here is what the
Okay, I changed the NLS_LANG setting on the oracle client to match
that of the server, and now it works. I found out about it here:
http://www.theserverside.com/discussions/thread.tss?thread_id=14634
On Mar 27, 1:27 pm, shday [EMAIL PROTECTED] wrote:
Hi,
The table is reflected, with one
the probable change that revealed this error is that oracle in 0.3.6
will by default apply cursor.setinputsizes() to all queries, which is
necessary for CLOB/BLOB. So encoding/NLS_LANG stuff probably became
more significant once cx_oracle has less need to guess about bind
parameters.
ive added the patchfile to the ticket and its part of a long list of
things i have to do.
On Mar 21, 2007, at 11:56 PM, 张骏 wrote:
so, youd just have people using postgres automatically and without
any control issue a SAVEPOINT SP after every single statement
execution ? what about the
Surprised no one has hit this one yet.
When issuing a series of deletes in a UOW, SA issues the bogus delete
statement
DELETE child where id = [1,2,3]
instead of using IN()
Test case attached. Seems to work in Sqlite even while issuing the bogus SQL
(which is probably why a unit test
20 matches
Mail list logo
