On Sat, Sep 13, 2008 at 5:41 AM, Stewart Smith <[EMAIL PROTECTED]> wrote: > On Wed, Aug 20, 2008 at 08:11:57PM -0700, Brian Aker wrote: >> I would personally never want to see FK across engines. It is a complete >> mess... Innodb has them, and that is fine to me. >> >> A cross engine FK is not on the list right now, and I doubt we will ever >> see it. It is not in the target list of features for the short term. > > and as soon as you start thinking about remote engines (NDB, Federated), > you quickly end up crying in the corner wishing it would all go away.
Apps built for the cloud (sharding, etc etc) have very little use for foreign keys, cross-engine or not. This is a reality that hits some people pretty hard. The realization that you have to give up on them is like losing your favorite snuggly blanket. I'd kind of like to rip them out of InnoDB, but I don't want to touch all that code. It's very scary. I'd call it the ugliest part of InnoDB's beautiful code, but there might be something uglier, I don't know. Indexing support itself is a little scary :) Who else on this list knew that InnoDB has a built in SQL parser and stored procedure language and writes itself SQL commands sometimes when it needs to do DDL operations?!?!? _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
