On 4-4-2013 21:25, Doug Chamberlin wrote: > On Thu, Apr 4, 2013 at 3:18 PM, Mark Rotteveel <m...@lawinegevaar.nl > <mailto:m...@lawinegevaar.nl>> wrote: > > On the other hand: using select * for anything other than ad-hoc queries > is bad. Should we support that? > > > Isn't it bad ONLY because the expanded list is unmanagable and > unpredictable? This proposal is a step toward removing that problem and, > therefore, is a big step in making "SELECT *" good rather than bad.
I would say the expanded list would remain unmanageable and unpredictable even if SELECT privileges would limit the expansion of *. An INSERT INTO TABLE SELECT * FROM TABLE WHERE ... will also break if a computed column is added, or I could be ignoring a new domain specific rules on which data I should copy or not, etc. It will might also break if a new column is added and I don't have the INSERT privilege, etc. An INSERT INTO TABLE (x, y, z) SELECT * FROM TABLE WHERE ... would also break if a column is added and I receive a SELECT privilege on that new column. Bottom line: IMHO SELECT * is bad if used in anything other than ad-hoc queries. Mark -- Mark Rotteveel ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
