Let me separate out: - MSSQL, Postgres, and .... offer views...
Views are select's that are offered "as if" they were tables, views into "raw" data - that is, they are convenient but innefficient views of data. My recommendation: DAL is not the place to implement this - leave this to the database. For example, if you have legacy data that is using primary key as "some_id", create a view in the database that exposes your legacy data with "some_id" as "id" and then model that view in DAL... That I think is a correct use of database views. Regards, and wishing you a Happy New Year, Yarko On Fri, Dec 26, 2008 at 4:55 PM, mdipierro <[email protected]> wrote: > > Give us an example. > > Massimo > > On Dec 26, 3:27 pm, "Alexandre Miguel de Andrade Souza" > <[email protected]> wrote: > > I know that is dificult to reproduce in a abstraction layer (DAL), all > > features of databases, but have one I need do ask: > > > > There is a way to make in DAL the same functionality of views in > Postgresql? > > > > Some kinds of data need query that use queries, and that funcionality > make > > it easier. > > > > -- > > ========================= > > Alexandre Miguel de Andrade Souza > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
