Except, in the analysis, it isn't really a problem related to or caused by the ORM itself or the SQL it produces, it's a subtle issue invoked by implicit casting...

Funny, though, in that this isn't how it worked IIRC for SQL Server 2000.

It seems to have been fixed in SP3.

That's a good article, except for a couple of things.

Why do people still literally use commas as field separators (unless they have to, because the tool/function/utility doesn't support anything else)?...

The '$' after the sheet name is required, whether it be a default sheet name like Sheet1, or one that's been renamed.

Another thing that works in order to find the gaps is to "interleave" the numbers together.

Say you have a table where the ID field (works with date values too) is...

"Theta Joins" also can be used.

For the given example in the article, the results should match for this query:

select c.*, o.*

from customers as c

left join orders as o

on...

Or...

select t1.c1, t1.c2, ...

from t1 join t2 on t1.c1 <= t2.c1

...

This has the potential to blow up, but it does make some date/time-related queries possible whereas putting the inequality in...

Yes, the administration of Oracle is a PITA compared to SQL Server, but from a (my) developer's perspective, it's a much bigger, varied set of legos to play with, as...

As a developer I'm not limited to doing EVEYTHING in SQL. For SQL2K I just count the rows coming into the record set. It's the hammer and nail thing. SQL2005...

Cool. It would be good to see it.

I came to my current job using SS2000 after using Oracle 9i. Although slightly obtuse and wordy, Oracle's partitioning for aggregate functions seemed...

So... the major problem with your article is that it posts no solutions for the problem at hand, or no pointers to where to look further to increase one's kungfu...

At least for US addresses, you could probably whip something out that normalizes the address entered by the data entry people. USPS.com does provide an API to do this.

If it...

Steve Jones wrote: "In most cases you take your T-SQL, move the variables to parameters and wrap the code in a CREATE PROCEDURE and RETURN. Error checking has to be...

Antares randomly pecked: "RoR can work against Stored Procedures (may take som checking on Google but I found several comments on). Just give yor justification as to why they must...