I've always considered "Sequal" the pronunciation of IBM's SEQUEL (Structured English Query Language) product and "es queue el" the correct pronunciation for the ANSI standard specification for SQL. Hence, I almost always say "es queue el" or "es queue el Server" or "My es queue el". I know I am in the minority with this, I'm sure when IBM changed their product name from SEQUEL to SQL the pronunciation stuck amongst IBMers. I don't have a ref handy, but I do remember that in their original SQL standard, ANSI declared that the official pronunciation is "es queue el" and referred to "sequel" as slang. The closest ref I have is this article which remembers the same. http://databases.about.com/od/sql/a/sqlfundamentals.htm have a good one.

mAreValo wrote:

So i was thinking about a new hobby and start writing games

Former VB programmer here as well (Since VBDOS, yikes) This may seam weird, but learn javascript. It's actually a good language (Not the DOM part of course, that is like trying to control chaos) but the language itself it has a lot of functional aspects that gives my tired mind quite a nice workout. This winter project for me is picking up "JavaScript: The Good Parts" (ASIN:0596517742, <$20) and a copy of Impact (JS game framework engine, http://impactjs.com/, $99) and trying my hand at some html5 games. Nice part is they are not expected to have awesome graphics, will run on any PC/Mac and most newer phones as well (iphone/windows/android) If you want to stick to more traditional languages, C# is great as you can use it with either the 360 or windows phones (with XNA) or windows pcs. Also Java is good as you can use it with PCs and android phones. Or even Google's app inventor is surprisingly robust and complex and you can easily make marketable games for android with that.... Let me know what you think/end up going with... (Note, if you do end up using javascript to manipulate the DOM, use a library like jQuery to at least make it bearable) -Jam

Hello all, long time lerker, normally just hang out in the code lounge, but I would really appreciate some help with mysql as I am new to it. I am a long time Sybase ASE user... so some things in mysql don't quick click for me as easy as they should... Ever deal with transactions in mysql? they seam to work not as I expect from my exp with sybase and mssql and just wanted to see how you handled em... first off, yeah, i know you have to use the innodb storage engine instead of the default myisam... so far that hasn't been a problem, I've heard people say that innodb just doesn't have the performance that myisam does but I haven't run into that... have you? plus it seams easy to convert between the two: "ALTER TABLE tablename ENGINE=INNODB;" anyway, how I know a transaction would look like this in a stored procedure in mysql: ................................cut................................. DELIMITER $$ DROP PROCEDURE IF EXISTS someProc$$ CREATE PROCEDURE someProc(IN params VARCHAR(80)) SQL SECURITY INVOKER BEGIN IF NOT EXISTS ([.. some condition ..]) THEN [.. do some stuff ..]; [.. do some stuff ..]; [.. do some stuff ..]; ELSE [.. do some stuff ..]; START TRANSACTION; [.. these are the UPDATE statements you want in a transaction ..] UPDATE sometable1 set somevalue=value WHERE something=something; UPDATE sometable2 set somevalue=value WHERE something=something; UPDATE sometable3 set somevalue=value WHERE something=something; UPDATE sometable4 set somevalue=value WHERE something=something; [.. these are the UPDATE statements you want in a transaction ..] COMMIT; [.. do some more stuff ..]; END IF; END$$ DELIMITER ; ................................cut................................. What I would expect the above to do, is that the statements in the transaction block either all fire or all fail/rollback if there was an error with one of them... this is how it was in sybase.. however, I end up with inconstant data in sometable3 and 4 if the update statement failed on sometable2. what I found I have to do, is call an explicit rollback on an error condition, so adding: DECLARE EXIT HANDLER FOR SQLEXCEPTION, SQLWARNING, NOT FOUND ROLLBACK; will call a rollback if an error occurs of type sqlexecption, sqlwarning or 'not found'. (basically, any error) I add it as the 1st line in the stored procedure after the begin block and now the above works as I expect it too (well al