On Friday 19 January 2007 11:03, Paul McNett wrote: > johnf wrote: > > Database --> schema --> tables. > > > > Therefore a Database can have many schemas. And each schema can have > > many tables. Within a schema a tablename must be unique but within a > > database you can have dup tableNames - because of schema.tablename. > > So... schemas are just another namespace, adding a bit more topography > to an essentially flat universe. > > Are we saying that no code changes are necessary to support schemas, > that user-level code merely needs to say: > > bizobj.DataSource = "mydatabase.myschema.mytable" > > or even: > bizobj.DataSource = "myschema.mytable" > > since the database is already set in the connection?
Yes I believe that is correct. At least that's how it works outside of dabo. So at the moment I don't see a problem with Phil's solution. I have only one exception. Phil's solution allows the user to see all schemas. So even if the user does not have access to a schema he sees it. But we might be able to filter the schema. Haven't tried yet. Phil also believes that is how Oracle works too. -- John Fabiani _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
