Besides, even for views, relational modeling specifies that all entries in a table or view need to be unique in that table/view. So in the absence of an obvious primary key for a view, a composite primary key (with all columns if necessary) is the Right Answer (TM) in this case.
Cheers, Leo On Wed, Nov 12, 2008 at 16:10, Gustavo Niemeyer <[EMAIL PROTECTED]> wrote: > Hi Gabriel, > >> I am trying to use Storm with MySQL views, but I get an exception that I >> didn't add a primary key, but there is no need to (since it's a view, >> unless I mistaking). How Can I get this to work? > > If you want to handle view entries as actual objects, right now Storm > needs a primary key to relate objects to view entries. It may be a > composed key, but it's needed. > > We may improve this in the future to make it work without object > identities for cases like this, but then the retrieved objects would > miss any relation to the database as soon as they are retrieved. > > -- > Gustavo Niemeyer > http://niemeyer.net > > -- > storm mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/storm > -- storm mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/storm
