Someone has recently made this claim without any supporting evidence,
and I responded with an example of the compiler/ORM running against
Oracle, truncating a long generated name, which had been aliased
twice, into a properly truncated name, results returned just fine.
This is a very
i've made something but before u jump on my overly generic ways of
coding, here the matrix to be tested:
matrix/possibilities:
A. mangling: for those longer, try 2 of same kind (in one parent),
both same size, beginning same but diff. at the end, with diff after
MAXLEN, e.g. sometable(
On Jun 23, 2008, at 3:27 AM, Egil Möller wrote:
I will make an effort to port them to the latest version before
posting them to trac.
OKbut I am *really really* curious what the bugs are. It would
be better for me to have a look to see what the preferred approach is
for them
On Jun 23, 2008, at 2:16 AM, [EMAIL PROTECTED] wrote:
i can make several tests about how the combination of tablename,
colname, seqname, indexname alone and some of them in pairs behave
around max_single_name_len=64 - below, at and above it. i've no iea
about schemas but i guess they can be
On Monday 23 June 2008 18:23:27 Michael Bayer wrote:
On Jun 23, 2008, at 2:16 AM, [EMAIL PROTECTED] wrote:
i can make several tests about how the combination of tablename,
colname, seqname, indexname alone and some of them in pairs
behave around max_single_name_len=64 - below, at and above
There are several bugs in how SA trunkates and mangles names for tables,
indices, columns etc. With postgres it's not so bad, because the cutoff
is at 64 chars (if you use elixir, set user_shortnames and you should be
ok). It's much worse when using e.g. Oracle (with its 32 char limit and
a
make a ticket at http://www.sqlalchemy.org/trac/query
(log in guest/guest but then put your email somewhere in ticket's
text)
and attach them all there.
or wait until Mike says so, maybe that existing ticket 820 can be
extended.
On Sunday 22 June 2008 15:26:38 Egil Möller wrote:
There are
On Jun 22, 2008, at 8:26 AM, Egil Möller wrote:
There are several bugs in how SA trunkates and mangles names for
tables, indices, columns etc. With postgres it's not so bad, because
the cutoff is at 64 chars (if you use elixir, set user_shortnames
and you should be ok). It's much
On Jun 22, 2008, at 7:50 AM, [EMAIL PROTECTED] wrote:
i hit some uncovered limitation, e.g. postgres truncating a name to 64
and then complaning about
sqlalchemy.exceptions.ProgrammingError:
(ProgrammingError)
_Assoc_SluzhebnoNaznachenie__originalno_ANazn_sluzhebni_naznach
is not a
Both #820 and #571 are fixed in 0.4 and 0.5.I'm looking forward to
seeing what else is wrong with long label names.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group,
On Sunday 22 June 2008 20:54:25 Michael Bayer wrote:
Both #820 and #571 are fixed in 0.4 and 0.5.I'm looking forward
to seeing what else is wrong with long label names.
from sqlalchemy import *
from sqlalchemy.orm import *
import sys
metadata = MetaData( sys.argv[1:] and sys.argv[1] or
the fix is along these lines, and its dependent on PG's behavior of
truncating, then appending _colname_seq. However, I've no idea
what it does when tablename + colname add up to more than 60, or when
colname alone is more than 60 - theres several variations here.
theres also many
On Sunday 22 June 2008 23:27:43 Michael Bayer wrote:
the fix is along these lines, and its dependent on PG's behavior of
truncating, then appending _colname_seq. However, I've no idea
what it does when tablename + colname add up to more than 60, or
when colname alone is more than 60 -
13 matches
Mail list logo
