This is not correct...

Assuming you are using only SQL to access the table, it's perfectly alright
to reference the table. As long as you are being lazy and using SELECT *.
SQL is decoupled by default. You can add columns without affect existing

*PUBLIC is *EXCLUDEd on any new SQL object by default when using SQL naming
simply because it's a security best practice to deny all by default and to
explicitly grant authorization.


On Fri, May 2, 2014 at 4:19 AM, D*B <dieter.bender@xxxxxxxxxxxx> wrote:

But the real important idea of sql is: You must not use a table in a DML
statement (never ever!!!) Use Views to decouple database implementation fro
programm logic! (That's why a table has public access exclude).

Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2015 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact