Re: Are generated SQL index name truncations harmless?
Re: Are generated SQL index name truncations harmless?
- Subject: Re: Are generated SQL index name truncations harmless?
- From: Joe Kramer <email@hidden>
- Date: Tue, 15 Mar 2011 22:39:07 -0700
I ran into this issue with Postgres as well. Because of my entity/relationship names and gigantic model, I ended up with several naming conflicts where two different index names were truncated to the same thing. It was kind of a pain, but it wasn't too hard to work around the issue. I don't think it is something that you need to worry about too much. I also didn't use migrations, so I have no idea how painful that would be.
Joe
On Tue, Mar 15, 2011 at 10:12 PM, Paul Hoadley
<email@hidden> wrote:
On 16/03/2011, at 3:39 PM, Chuck Hill wrote:
> I think it should be fine as the truncation would be consistent. Unless maybe in a later PG version...
Ha! I also remember what happened last time I _assumed_ some behaviour at the JDBC level... Anyway, no Migrations here. I'm leaving it alone.
--
Paul.
http://logicsquad.net/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (
email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden