ANSI SQL Is Dead

Question

ANSI SQL Is Dead

Viewing 3 posts - 16 through 17 (of 17 total)

You must be logged in to reply to this topic. Login to reply

Steve Booth-352727 SSC Journeyman Points: 88 More actions · Answer 1

In my application, while the SQL Code itself is less than the front-end code, the business process logic is modelled in the database so as to be UI independent. In other words, in the app that I'm using 3K lines is UI, 20K is database base related stuff. The SQL code itself is the glue that marries the Database to the business process logic.

Just my $.02

Steve Booth...

Loner SSC-Insane Points: 21279 More actions · Answer 2

I started writing Oracle SQL and PL/SQL in 1992. It was confusing and hard to debug. When I started working SQL Server in 2000 using ANSI SQL standard especially using the 'JOIN' statement. It was much better and easier to debug. I even used ANSI SQL to write Oracle SQL.

I like ANSI SQL, I hope it is not going to die, but maybe improve in some areas.

webrunner SSC-Dedicated Points: 31885 More actions · Answer 3

I find it hard to disagree with the gist of the editorial. It was especially effective to have us imagine life without certain functions that are nonstandard but essential to a given database.

However, I think there is a little more to be said. I am no expert on ANSI standards, but I think the C programming language had similar issues, and the solution was to update the standard. Updating the standard doesn't necessarily resolve all problems, but it is better to have a 2006 ANSI standard than a 1992 ANSI standard.

It is also good to keep in mind that many vendors are looking to make money by adding nonstandard features. By and large the features are good, but occasionally they aren't, and they may promote practices that are worse rather than better. I am thinking particularly of people who see some cool functions in a database and then define their database requiring the function in order to make the database at all useful. Then, if the time comes to migrate to a new database, the next database can't do the function or the changes are a big headache.

I agree that a foolishly consistent standard is the hobgoblin of little minds. But standards have their place. That's what makes it possible for one light bulb to fit so many sockets.

-------------------
A SQL query walks into a bar and sees two tables. He walks up to them and asks, "Can I join you?"
Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html