On Monday 26 October 2009 05:54:04 pm John Fabiani wrote: > dabo Commit > Revision 5495 > Date: 2009-10-26 17:54:03 -0700 (Mon, 26 Oct 2009) > Author: Johnf > Trac: http://trac.dabodev.com/changeset/5495 > > Changed: > U trunk/dabo/db/dbPostgreSQL.py > > Log: > removed "pg_table_is_visible" from the getFields method. It was preventing > me from using schemas other than 'public'. I see no reason for it being > in the SQL statement. I guess no one ever tested the statement against a > different schema - other than 'public'. > > I have always wanted to remove all the if's, elif's to determine the Dabo > data type. The dict I have added make it much more straight forward to see > what may be missing from the Postgres data types and what the associated > Dabo type is.
Larry has started a discussion regarding the removal of the "pg_table_is_visible" function from the SQL statement. By removing it all users are able to see the tables and retrieve field names. Even if the users search path does not include the schema. By including the statement the getFields method will return nothing if the search path does not include the schema. Note change the search path as follows: ALTER USER test SET search_path TO schema1,schema2 I always want the field names to be available because it has nothing to permissions to write or read. The getTables method handles the issue regarding access - so I see no reason to prevent reading the column properties. On the other hand I'm open to discussion on the matter. For now I'm leaving the statement out of the SQL string. Johnf _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
