> > I suppose these are the ways with Databases. They don't work the way > > we like them to. > > So please adjust with it. For this matter I think, any RDBMS will be > > doing their or paddings to the scripts when they are loading it in > > memories. > > But that doesn't make it right. > > Specifically, I seem to remember from the SQL standard that the use of > database.table.field is undesired (or schema.table.field if you don't > use MySQL) and instead database.table should be aliassed. In that case > it should be: > CREATE VIEW test.myview2 AS select alias.c1 AS t0 from test.t alias; > > Further, I would like to second Martijn's opinion regarding backticks. > It is bad enough that the SQL standard double quote isn't used, let's > not make it worse by including unwanted backticks.
I also mentioned a more "real life" example - I just realized I send that to the "internals" list, and not to this one. You can view my message here: http://lists.mysql.com/internals/17270 If I would be a user of MySQL 5 (and I am, working on a developer tool and all), I would be seriously ticked off if this would make it into the production release... Have a look at the message at the URL above and tell me this is the "right way" to bring a system into production and keep it maintainable. With regards, Martijn Tonies Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL Server. Upscene Productions http://www.upscene.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
