| |
A Uniform Query To The Community
By Michael Marr
Expert Author
Article Date: 2010-06-08
The language of SQL is a lot like the English language. You have North American and Great Britain dialects of the language, not to mention significantly varying degrees of those dialects broken down amongst the geographical regions in which they're spoken.
And so is the fate of the Structured Query Language. Although the base of the language remains somewhat intact, programming in Oracle, Microsoft SQL, PostgreSQL, or other SQL extensions when you're from a MySQL background becomes painfully difficult at times (or switch MySQL with any of the other languages and the same occurs). The line between proper SQL and the corner of the SQL world we belong to become blurred, and only when we are forced to use another SQL environment are we painfully reminded of this.
The solution? A community project to convert SQL from one extension to the another. This way, when someone gets a project requiring them to use a foreign SQL engine, they can proudly take on the project, writing it in their own version of SQL first, and then convert using this magic tool. Does this project already exist? Not that I could find. If so, please let me know so I can update this article. Why can't I start it? I could, and probably will. What I'll need though is help, in more ways than just this project, but we'll concentrate on the project for now. I am proficient with MySQL (and now familiar with T-SQL thanks to a recent project), but hardly have the capacity to relate the nuances of other languages, e.g. converting MySQL's LIMIT to TOP.
So my fellow SQL Professionals, let us unite! No longer shall we be afraid to venture into Oracle, PostgreSQL, MySQL, or whatever other SQL language the world throws at us, but rather, let us be properly equipped to take on whatever challenges we are given!
About the Author:
Michael Marr is a IT staff Writer for WebProNews.
|
|
