Making really sure



  • <table width="90%" border=0 cellpadding=0 cellspacing=0 border=0  border=0>



  • Invalid HTML != WTF



  • @AccessGuru said:

    Invalid HTML != WTF

     

    AccessGuru != DBA 



  • Dude, I've built over 30 enterprise-level ODBC database apps.  I bet you can't even program in sequel.  



  • @AccessGuru said:

    Dude, I've built over 30 enterprise-level ODBC database apps.  I bet you can't even program in sequel.  

     

    Sequel?



  • @AccessGuru said:

    Dude, I've built over 30 enterprise-level ODBC database apps.  I bet you can't even program in sequel.  

     

    SQLs not a programming language, it's a query language, so noone can really program in it. Procedural augmentations to SQL such as PL/SQL are a different matter.



  • @jefg said:

    <table width="90%" border=0 cellpadding=0 cellspacing=0 border=0  border=0>

    I don't suppose you can tell us which WYSIWYMG editor created this?



  • @drinkingbird said:

    @AccessGuru said:

    Dude, I've built over 30 enterprise-level ODBC database apps.  I bet you can't even program in sequel.  

     

    SQLs not a programming language, it's a query language, so noone can really program in it. Procedural augmentations to SQL such as PL/SQL are a different matter.

     

    He really called you out on this one, didn't he GURU???



  • @drinkingbird said:

    SQLs not a programming language, it's a query language, so noone can really program in it. Procedural augmentations to SQL such as PL/SQL are a different matter.

    In b4 someone mentions "Turing completeness".



  • Enjoy your mug.



  • @AccessGuru said:

    Dude, I've built over 30 enterprise-level ODBC database apps.  I bet you can't even program in squirrel.  

    FTFY


  • I actually built a very basic computer out of squirrels once.  It consisted of 64 squirrels in an array of boxes, each box having two rooms (or states).  When I wanted to increment the value of a register, a food pellet was dropped into a particular set of boxes.  I was able to do a few addition and subtraction calculations before the system had an overflow (some of the squirrels chewed their way out of the boxes).  



  •  @TheDude said:

    @drinkingbird said:

    SQLs not a programming language, it's a query language, so noone can really program in it. Procedural augmentations to SQL such as PL/SQL are a different matter.

     

    He really called you out on this one, didn't he GURU???

    Yes, he did.  But the fact of the matter is that I wrote a Sequel compiler in phpGTK for importing into DB2 and wrapped it in a Joomla plugin.  I don't hear you making such claims. 



  • @AccessGuru said:

    30 enterprise-level ODBC
     

    The real WTF is someone posting nonsense like this, and using "AccessGuru" as a username in these forums also has a sig that mentions "World class IT solutions". Access/Guru/World class solutions/enterprise-level ODBC? Can you say "oxymoron"?



  • You wrote a Sequel(Lisp or SQL?) compiler in a web scripting language using a GUI framework, and then did som completely irrelevant things using a database and a CMS? Sounds like a really good setup for someone aspiring on getting a Swampy-award(tm).



  • @KenW said:

    You wrote a Sequel(Lisp or SQL?) compiler in a web scripting language using a GUI framework, and then did som completely irrelevant things using a database and a CMS? Sounds like a really good setup for someone aspiring on getting a Swampy-award(tm).

     

    It was for Sequal Server.  I was going to use ASP.NET but I'm still trying to install the framework.  



  • @AccessGuru said:

    It was for Sequal Server.  I was going to use ASP.NET but I'm still trying to install the framework.  
     

    WTF is 'Sequal Server'???

    Jesus christ.... do you mean MSSQL Server?

     

    I think KenW might have you pegged correctly...

     @AccessGuru said:

    I was going to use ASP.NET but I'm still trying to install the framework.  

    I am sure you mean the .NET framework, which is incredibly quick and easy to install.... 

    I mean wow.... just wow...



  • @AccessGuru said:

    @KenW said:

    You wrote a Sequel(Lisp or SQL?) compiler in a web scripting language using a GUI framework, and then did som completely irrelevant things using a database and a CMS? Sounds like a really good setup for someone aspiring on getting a Swampy-award(tm).

     

    It was for Sequal Server.  I was going to use ASP.NET but I'm still trying to install the framework.  

    There's comedy, there's high comedy, and then there's your insane attempt to impress us.



  • @AccessGuru said:

    Dude, I've built over 30 enterprise-level ODBC database apps.  I bet you can't even program in sequel.  

     

    I know some people pronounce it "sequel" - but I don't because it just seems silly*

    Whatever people want to pronounce it, it is pronounced that way, not written that way. Or do you also write ay es pee dot net?

     

    *Note: I am not a DBA, maybe if I were one all the other DBAs would laugh at me calling it S-Q-L!



  • You are so amateur. Just yesterday I made an inventory app with Cold Fission that merges XML and CSV data in YAML, and then inputs into a BLOB field of a File Maker Pro database. It all runs on a Palm so that we can scan RFIDs in the warehouse.



  • @MasterPlanSoftware said:

    @AccessGuru said:

    It was for Sequal Server.  I was going to use ASP.NET but I'm still trying to install the framework.  
     

    WTF is 'Sequal Server'???

    Jesus christ.... do you mean MSSQL Server?

    Oh no, I cringe on the "Sequel Server" pronunciation ... but "Sequal"? Sounds like the jigawatt syndrome!

    Ok, I'm back on working with my deebeetoo and saibeize projects...



  • @danixdefcon5 said:

    I cringe on the "Sequel Server" pronunciation
     

    I don't. I firmly believe that only an idiot would care if you call it S-Q-L or sequel. But to write it out? Holy jesus. That is a whole different level.

     

    And yeah, we have already had that flamewar, so spare us your feeling on the subject. Anyone who cares has too much time on their hands.



  • @MasterPlanSoftware said:

    I don't. I firmly believe that only an idiot would care if you call it S-Q-L or sequel. But to write it out? Holy jesus. That is a whole different level.

    And yeah, we have already had that flamewar, so spare us your feeling on the subject. Anyone who cares has too much time on their hands.

    Not really concerned on pronunciation; personally I refer to SAP as "sap", CICS as "sicks", RACF as "rack-F" and such. But I'm not about to write "Rack-F" ... kind of reminds me when we got a requirement for creating new users in the EL DAP server...

    Anyway, I'd definitely not put Access as something I'm an expert with. And writing "Sequel Server" in a C.V. isn't going to look so bright...



  • @GettinSadda said:

    I know some people pronounce it "sequel" - but I don't because it just seems silly*

    *Note: I am not a DBA, maybe if I were one all the other DBAs would laugh at me calling it S-Q-L!

     

    I know we've had this discussion here before (probably many times) but if I recall correctly the pronounciation of SQL as 'sequel' appears to be Microsoft specific.



  • @Hitsuji said:

    I know we've had this discussion here before (probably many times) but if I recall correctly the pronounciation of SQL as 'sequel' appears to be Microsoft specific.

    No, it comes from the pre-cursor to SQL called SEQUEL developed by IBM.  When SQL became an ANSI standard the "official" pronunciation became S-Q-L. 



  •  Sorry, maybe I should have made myself a bit clearer. Linux developers tend to stick to open standards a lot more than Windows developers, that include pronounciations. SQL as an ANSI standard is NOT SEQUEL, it's predescessor, therefore to disguish the two the Linux community almost always say 'Es Queue El' and not 'Sequel'. Windows developers tend to be very different and 'traditional' when it comes to these kinds of things and specifically MS where possible will publically give a very pronouncable rather than naming a product as an acronym. If you watch any webcasts on MS SQL you will see a majority (from what I have seen myself) of MS employees reffer to MS SQL Server as 'Sequel Server'. this had a tendency to rub off on Windows specific and MS SQL Server specific developer. Hence my comment that the Pronounciation of SQL as Sequel seems to MS specific.



  • @Hitsuji said:

    this had a tendency to rub off on Windows specific and MS SQL Server specific developer. Hence my comment that the Pronounciation of SQL as Sequel seems to MS specific.
     

    You don't think that it might have something to do with many open source crusaders being pedantic, shallow and elitist?



  • @MasterPlanSoftware said:

    You don't think that it might have something to do with many open source crusaders being pedantic, shallow and elitist?

     

    Yes that too. 



  •  @MasterPlanSoftware said:

    @Hitsuji said:

    this had a tendency to rub off on Windows specific and MS SQL Server specific developer. Hence my comment that the Pronounciation of SQL as Sequel seems to MS specific.
     

    You don't think that it might have something to do with many open source crusaders being pedantic, shallow and elitist?

    no more than microsoft elistists

     

    every camp has their dickwads.



  • @Kazan said:

    every camp has their dickwads.

    Agreed. Some just choose to foul up otherwise unbiased forums with their FUD.

    Amazing what those 'dickwads' will do just to be trolls.



  • @Hitsuji said:

    Linux developers tend to stick to open standards a lot more than Windows developers...

    [citation needed]

     

    @Hitsuji said:

    ...that include pronounciations.

    You have got to be kidding me.

     

    @Hitsuji said:

    SQL as an ANSI standard is NOT SEQUEL, it's predescessor, therefore to disguish the two the Linux community almost always say 'Es Queue El' and not 'Sequel'.

    ANSI SQL is a bit different than SEQUEL but for the most part they are identical.

     

    I am not a Microsoft developer but I have always called it "sequel server".  I used to call the language S-Q-L and my database My-S-Q-L, but I have since switched to saying "sequel" all the time because it flows a hell of a lot better.  It doesn't make a different what you call it, but to me saying all three syllables is a lot less fluid than "sequel".  It would be like saying R-A-M instead of "ram", S-A-S-L instead of "sassle" or W-Y-S-I-W-Y-G instead of "wizzywig". 



  • @morbiuswilters said:

    I used to call the language S-Q-L and my database My-S-Q-L, but I have since switched to saying "sequel" all the time because it flows a hell of a lot better.  It doesn't make a different what you call it, but to me saying all three syllables is a lot less fluid than "sequel".  It would be like saying R-A-M instead of "ram", S-A-S-L instead of "sassle" or W-Y-S-I-W-Y-G instead of "wizzywig". 
     

    100% agreement.



  • @MasterPlanSoftware said:

    @morbiuswilters said:

    I used to call the language S-Q-L and my database My-S-Q-L, but I have since switched to saying "sequel" all the time because it flows a hell of a lot better.  It doesn't make a different what you call it, but to me saying all three syllables is a lot less fluid than "sequel".  It would be like saying R-A-M instead of "ram", S-A-S-L instead of "sassle" or W-Y-S-I-W-Y-G instead of "wizzywig". 
     

    100% agreement.

    98% agreement.



  • @bstorer said:

    @MasterPlanSoftware said:

    @morbiuswilters said:

    I used to call the language S-Q-L and my database My-S-Q-L, but I have since switched to saying "sequel" all the time because it flows a hell of a lot better.  It doesn't make a different what you call it, but to me saying all three syllables is a lot less fluid than "sequel".  It would be like saying R-A-M instead of "ram", S-A-S-L instead of "sassle" or W-Y-S-I-W-Y-G instead of "wizzywig". 
     

    100% agreement.

    98% agreement.
     

    99% agreement.

    But I never say "sassle". Of course, I never say S-A-S-L or SASL either. 



  • If you guys weren't all lame VB hackers, you'd realize that the correct pronunciation is 'structured query language'.



  • Hats off to AccessGuru for a successful troll that's actually funny.


Log in to reply