Right. You are explicitly defining the primary/foreign keys on the views in your ORM layer. This can be done in either SO or SA. It just doesn't work with SQLSoup.
Jorge Godoy wrote: > jose <[EMAIL PROTECTED]> writes: > > >> John Lavoie wrote: >> >> >>> Then your view is not *well defined*. Your database doesn't know what >>> the primary key is on the view, so SQLSoup won't be able to determine >>> this either. You are adding it in the ORM layer. >>> >>> If your database supports primary and foreign keys on views then you can >>> set these up and SQLSoup will work on the view. Oracle supports this, I >>> don't know about others, >>> >>> >> PostgreSQL doesn't. :-( >> > > I'm using SQLObject with PostgreSQL and mapping my views explicitly. It works > perfectly and besides having an extra class (you'd have it anyway) there's > nothing that I miss with it. > > If I had RULEs in place I could even update data, insert, delete, > etc. directly from the view. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
