Well is it SQL or isn't it?
-
I had a WTF :wtf: moment while reading the documentation for a "database" system I'm evaluating (name changed to protect the guilty): " The precedence of arithmetical operators in SQL expressions differs from the SQL-92 standard. Fubar's SQL parses arithmetic expressions in strict left-to-right order, with no operator precedence. " I'm certainly glad I read that before trying to do any actual work with it. I wonder whether or not anyone's been bitten by it. Certainly there's a work-around (lots of infuriating silly parentheses), but does anyone else find this unacceptable in a modern database system?
-
I had a WTF :wtf: moment while reading the documentation for a "database" system I'm evaluating (name changed to protect the guilty): " The precedence of arithmetical operators in SQL expressions differs from the SQL-92 standard. Fubar's SQL parses arithmetic expressions in strict left-to-right order, with no operator precedence. " I'm certainly glad I read that before trying to do any actual work with it. I wonder whether or not anyone's been bitten by it. Certainly there's a work-around (lots of infuriating silly parentheses), but does anyone else find this unacceptable in a modern database system?
Yep, it's unacceptable. Having to kludge the precedence with parentheses will not only be mind-numbing extra work a but a maintenance headache. No excuse for this, since most earlier SQL standards specified normal operator precedence. I'd say it failed the evaluation because of non-standard precedence creating an error generator and maintenance killer.
-
I had a WTF :wtf: moment while reading the documentation for a "database" system I'm evaluating (name changed to protect the guilty): " The precedence of arithmetical operators in SQL expressions differs from the SQL-92 standard. Fubar's SQL parses arithmetic expressions in strict left-to-right order, with no operator precedence. " I'm certainly glad I read that before trying to do any actual work with it. I wonder whether or not anyone's been bitten by it. Certainly there's a work-around (lots of infuriating silly parentheses), but does anyone else find this unacceptable in a modern database system?
We want that name... to stay away. :-D
If you truly believe you need to pick a mobile phone that "says something" about your personality, don't bother. You don't have a personality. A mental illness, maybe - but not a personality. - Charlie Brooker My Blog - My Photos - ScrewTurn Wiki
-
I had a WTF :wtf: moment while reading the documentation for a "database" system I'm evaluating (name changed to protect the guilty): " The precedence of arithmetical operators in SQL expressions differs from the SQL-92 standard. Fubar's SQL parses arithmetic expressions in strict left-to-right order, with no operator precedence. " I'm certainly glad I read that before trying to do any actual work with it. I wonder whether or not anyone's been bitten by it. Certainly there's a work-around (lots of infuriating silly parentheses), but does anyone else find this unacceptable in a modern database system?
Well that was easy to find: InterSystems Caché SQL[^].
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007 -
Well that was easy to find: InterSystems Caché SQL[^].
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007So much for protecting the guilty.
-
So much for protecting the guilty.
The exact quote from the site made it very easy to find. :-D
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007 -
The exact quote from the site made it very easy to find. :-D
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007(I know)
-
We want that name... to stay away. :-D
If you truly believe you need to pick a mobile phone that "says something" about your personality, don't bother. You don't have a personality. A mental illness, maybe - but not a personality. - Charlie Brooker My Blog - My Photos - ScrewTurn Wiki
See Dave's post. I looked at that particular database some years ago, and never looked back at it.
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
-
Well that was easy to find: InterSystems Caché SQL[^].
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007I took a look, briefly, some years ago at that database, and never really got into it, even though they have those odd ads in Dr. Dobb's Journal all the time...
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
-
I took a look, briefly, some years ago at that database, and never really got into it, even though they have those odd ads in Dr. Dobb's Journal all the time...
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
It says its the fastest database though? I wonder how it compares to say sqlite
-
It says its the fastest database though? I wonder how it compares to say sqlite
StevenWalsh wrote:
I wonder how it compares to say sqlite
I am not sure. I haven't really worked with sqlite and I hear alot of good things about it. I am tempted to put together a Northwind style of a database, build it on a number of different database platforms, test out performance and write up an article here about the results. Hmmmm... :)
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
-
StevenWalsh wrote:
I wonder how it compares to say sqlite
I am not sure. I haven't really worked with sqlite and I hear alot of good things about it. I am tempted to put together a Northwind style of a database, build it on a number of different database platforms, test out performance and write up an article here about the results. Hmmmm... :)
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
That would be a very interesting article.
-
That would be a very interesting article.
There are many different approaches to this, and I have to figure which are the most meaningful and what assumptions should be made...
"The clue train passed his station without stopping." - John Simmons / outlaw programmer
-
There are many different approaches to this, and I have to figure which are the most meaningful and what assumptions should be made...
"The clue train passed his station without stopping." - John Simmons / outlaw programmer
One of the first assumptions would be that proper order of operations is followed. Be sure to test it though.
-
One of the first assumptions would be that proper order of operations is followed. Be sure to test it though.
Thanks for the tip. I was thinking along the lines of building a test suite app where the user can choose which database platforms he/she has, run tests on the throughput of SELECT statements fetching various numbers of rows ( i.e., first pass would get first 100, then second pass, first 200, then third pass, the first 400 - doubling each time until a certain point, say 1,600.), do the same for INSERTS, UPDATES, and DELETES. One item of caution would be that more databases they choose from, the longer the test has the potential to take. There could be network considerations to take into place. As you can see, this could end up being a pretty big deal. Maybe just start of simple, then advance it. I could just go on and on :rolleyes:
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon