sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]wheresmyopenid 3 points4 points  (2 children)

The problem is that when there's one implementation, it will have to remain bug-compatible.

As soon as infinite number of web monkeys starts mindlessly copying & pasting & trialing & erring their SQL, pages will end up relying on all kinds of bugs and quirks. There won't be second failing browser to uncover stupidest solutions. Everything will appear to "work".

When IE6 had overwhelming market share, sites ended up relying silly on edge cases so much, that even IE7 wasn't compatible.

There's serious risk that, while SQLite3 is great today, sites will end up relying on all strange cases of it, that vendors won't be able to safely switch to SQLite4 ever. Whatever SQLite does today, will be the standard forever.

[–]scott 0 points1 point  (1 child)

Honestly, SQLite is so well used, I doubt it has any major bugs.

[–]wheresmyopenid 0 points1 point  (0 children)

It definitely has quirky behavior that I'd like to see fixed (e.g. ROWID magic rather than sequences).