Uwe Grauer (at googlemail) wrote: > johnf wrote: >> Hi, >> >> I would like to know how others (Phil?) are using schemas. >> >> I want to add more support for schema's in postgres. But I have never had a >> need for anything but a public schema. I.e. >> >> Within a single select statement does one have multi- schemas? >> >> "Select a.somefield, b.somefield From schema1.table a schema2.table b" >> >> >From what I understand the use schema is to separate users use of tables. >> >IOW >> just added security. But like I said I have never used schemas - but a >> public one. So please add to the discussion. >> >> Thanks > > Not all database admins are allowing selects on the schema. > So depending on schemas is only an option if you would use it for > development. >
This sounds like another case for generating a table/query/cursor definition file at design time that becomes part of the app, and may cause problems if the table structure gets changed and the config file not updated. (A risk I am ok with.) In fact, I was wondering why dabo didn't have something similar to a VFP view. actually, I think it does, just not being exploited / advertised. I also think I have seen some of the implementation slip into the biz layer (bad bad bad.) What I mean by a VFP view: some wad of settings that the data layer uses to read/write the server. the settings define how to read (SELECT or SP call) and write (PK, updateable fields, where type.) So all the stuff you can dbGetProp() from a vfp view. Carl K _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
