On May 23, 2008, at 10:02 PM, Brandon Goldfedder wrote:
Michael,
Yes - that is what I am doing now :
ForeignKey(schemaname.tablename.colname)
and I have things working. (see example 3).
My problem is these steps
seem really ugly and a lot more work than it should be to get things
MIchael,
Thanks for your help on this - I agree I want to get beyond a mess
here regardless if it is 'working'
Here are 3 tables that demostrate the issues (with the changes I
needed to do use_alter, modify schema.py, hardcode in schema name to
ForeignKey and tables). I want the model
thank you , this was an old ticket #709 and is fixed in r4814 of the
0.4 branch and r4813 of trunk. remove the usage of owner, it is
synonymous with schema (as it is in oracle itself -
http://www.dba-oracle.com/t_schema_components_owner_user.htm
) , as well as all the other hacks.
On
Michael,
Great - that handles the create_all(checkfirst issue)
Any fix for the ix_ table name taking into account Oracle name limits
in schema.py?
Thx,
Brandon
On May 24, 7:37 pm, Michael Bayer [EMAIL PROTECTED] wrote:
thank you , this was an old ticket #709 and is fixed in r4814 of the
0.4
old bug, I think its #820. we generate a bad name in that case. Try
using the schema.Index() or schema.DDL() construct for now as a
workaround (I'm not entirely thrilled about the index=True option on
Column in general).
On May 24, 2008, at 8:20 PM, Brandon Goldfedder wrote:
All,
So have a 'working' solution but think it is pretty bad... Someone
MUST have a better solution. Here is what I had to do:
1. Have create_all explictly not test for tables existing (or else it
finds it in wrong schema)
create_all(checkfirst = False)
2. Explictly set the schema and owner
On May 23, 2008, at 3:10 PM, Brandon Goldfedder wrote:
All,
Perhaps someone can help me here since I am in that 'bad place' where
I am retrying things again and getting deeper than I want into it.
I am trying to create a database (using elixir model although the
problem appears to be in
Michael,
Yes - that is what I am doing now :
ForeignKey(schemaname.tablename.colname)
and I have things working. (see example 3). My problem is these steps
seem really ugly and a lot more work than it should be to get things
working portably and reliably - thus my question on if this is best
