Firebird .NET provider and calling sp with parameters

Firebird .NET provider has ability to create parameterized queries. Both named and unnamed parameters are supported. Everything works as you expect with select, insert, delete or update commands. The tricky part comes with stored procedures. Unlike MS SQL, that has direct support for named parameters, in provider, we’re parsing parameter names and we’re sending it to server “in right order”, so developer doesn’t need to know, that internally parameters were send unnamed.

Me on Marc Fleury on Sun purchase of MySQL – replaceable lamp bricks

The last post was supposed to be this one, but I got distracted on how I found it

Whether you’re using Postgres, SQLite, Oracle, Microsoft SQL Server, HSQLD, Firebird, Derby, or whatever, you’re benefiting from the popularity of MySQL. If you’re still using Progress, dBase, or Sybase, maybe not.

My point is that MySQL did for databases what Netscape did for the internet, what Apache did for web servers, what Star Office did for alternate word processors, what Sendmail did for email servers, and what JBoss did for J2EE.

[ED Here is my reply :Bricks can be replaced in the lamp
Why they always forget the MTA or DNS?
They are critical parts of the clusters
Sendmail is replaced by postfix or qmail if you are a sane person (in ubuntu postfix is by default)
Apache is replaced by lighttpd and nginix – better webservers IMHO
mysql by firebird or postgresql
linux kernel is good enough and is better than win or solaris (if you want wamp or samp)

php can be replaced by ruby or perl or python (if it becames bloated like java in version 6.x) ]

1 218 219 220 221 222 296