Mark Aufflick said: > I feel a good old fashioned usenet style flame war coming on =) Slashdot has flame wars, all we have are friendly argument with as outcome learning more about our favourite and other products.
> In Sybase, NULL matches NULL in a search clause (by default - as Yes. I personaly think it is a good extention to be able to just compare to NULL directly instead of having to detect in code that the input value is null and change your query string accordingly. It may not be standard practice, but it sure as hell makes a lot of sense. Postgres and MySQL allow you to do "where foo = null" without warning or error but simply don't return rows. > established), but NULL will never match anything (not even itself) in > a join ( You mean just like in Postgres and MySQL? (not tried in Oracle) I don't really see how the two are related. One is good practice done by other databases too and one is, well, nothing to write home about and probably good behaviour the ANSI SQL standard should prescribe. > You are probably correct. (Although I grew up on Applesoft basic and I > don't like VB!) There is one thing I dislike more than VB itself: VB programmers. I mean people who ONLY know hot to program VB. The kind that make their function return "-999" on error instead of telling you what the f*** is actually wrong. (a stacktrace would be nice, oh wait, VB doesn't do those!) > Should we call a truce? ;) Don't be silly! :) Bas. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
