You have commented 339 times on Rantburg.

Your Name
Your e-mail (optional)
Website (optional)
My Original Nic        Pic-a-Nic        Sorry. Comments have been closed on this article.
Bold Italic Underline Strike Bullet Blockquote Small Big Link Squish Foto Photo
India-Pakistan
Bush's trip to Pakistan today not without risks: White House
2006-03-03
Posted by:Fred

#18  Like Quayle, Djohn?
Posted by: Eric Jablow   2006-03-03 15:45  

#17  Just boys playing with stuff.
Posted by: phil_b   2006-03-03 09:47  

#16  lol good thread
Posted by: Jan   2006-03-03 09:40  

#15  Damn. Fix one thing, break another. It works now.
Posted by: Fred   2006-03-03 09:00  

#14  Like you're dealing with people capable of rational thought, djon66.
Posted by: gromgoru   2006-03-03 08:32  

#13  That's what I say to friends, that Chenny is Bush's bullet proof vest. They kill Bush they get Chenny and that scares LLL even more .:)
Posted by: djohn66   2006-03-03 08:17  

#12  Back on topic...
The risk is not all to Bush. Almost three years of President Cheney could be a considerable additional risk to our foes.
Posted by: Halliburton Revenge Div.   2006-03-03 08:13  

#11  If you want fun with SQL and purists check the news groups for Joe Celko ... some good arguments there and good info on both sides of the coin.

SQL Server and a few others use single quote / tick instead of double. If using SQL server or another that does this, a parameter based stored procedure (or compiled procedure in oracle) is MUCH better than sending the query or update as a string to the engine. You get true paramter checking and none of this single / double quote problem ... esp if the data contains special characters.

Also, you've abstracted your data access from the logic, so when you have to change things, esp if you change engines a lot, you don't have to regression test your logic or reverify it ... or simply you don't have to dig through logic to update a simple query.

Just some thoughts / pointers.
Posted by: bombay   2006-03-03 08:08  

#10  Fred changed DBs like socks - dunno what he ended up with - but the double-quote also appeared to be the culprit in the error msg for submitting a link-only article. Hey, whadda I know. ;-)
Posted by: .com   2006-03-03 06:48  

#9  Apropos of not much at all, Chris Date's Guide to the SQL Standard is a classic. Easily the best book of its type ever written. I used to be forever going around the office tracking down who had 'borrowed' my copy.

I recall a " is a reserved character in the standard.
Posted by: phil_b   2006-03-03 06:41  

#8  Looks like the SQL is objecting to the use of the double-quote as parm delimiter...
Posted by: .com   2006-03-03 06:14  

#7  I got a similar SQL error trying to post an article link.

Brokeback to the Future

Heh. Love parody trailers.
Posted by: .com   2006-03-03 03:42  

#6  um....yeah.
Posted by: 2b   2006-03-03 03:00  

#5  Oops, .com's right. An email address to report bugs would be a good idea.
Posted by: phil_b   2006-03-03 02:29  

#4  Heh - you should delete that comment, Fred. It gives away waaay too much Field Id info, lol.
Posted by: .com   2006-03-03 02:12  

#3  Fred, just tried to post an article and got this,

Posted by: phil_b   2006-03-03 02:08  

#2  I fixed it.

Damn them.
Posted by: Fred   2006-03-03 00:13  

#1  
bug report extracted - thanks
Posted by: phil_b   2006-03-03 00:09  

00:00