Re: Here we go again...WebDNA - SQL- Stored Procedures
This WebDNA talk-list message is from 2006
It keeps the original formatting.
numero = 66718
interpreted = N
texte = Well said. Have you found a way to use MySQL stored procedures with webcat? If so I would love to know, I can't wait to use them with webcat. nitai@computeroil.com wrote: > Let's put it in simple word: > > Once you start using SQL syntax and use some of the languages very own features like JOIN or UNION you simply won't go back to use flat files. > > Instead of using a search within a search and then a lookup within that founditems (all true real world examples) and you see how easy this is done with ONE SQL statement it should start making sense to everyone :-) > > It just open up a new world of possibilities. Imagine you have one single location for all your data and that location does not even has to be in house. That other systems can connect to it as well is a life saver sometimes. > > Now when you start with stored procedures you have another story where your database does all the work for you and not the webserver anymore... > > I don't think this is a conversation of the scripting language but more why to use SQL. > > Nitai > > -- > eContentPark - Enterprise Digital Asset Management > eServices - The complete SupportSuite > eSurvey - Online Questionnaire made easy > Redakto CMS - Content Management that simply works > > ComputerOil® AG > Neugutstrasse 66 > 8600 Dübendorf / Switzerland > Telefon +41 (0)844 44 55 66 > > info@computeroil.com > http://computeroil.com > > >> -----Original Message----- >> From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com] On Behalf Of >> Alex McCombie >> Sent: Dienstag, 4. April 2006 05:45 >> To: WebDNA Talk >> Subject: Re: Here we go again...WebDNA - SQL- Clustering >> >> Lol the funny thing everyone is so passionately debating the WebDNA tables >> VS. SQL like they are sworn enemies. >> >> Let me help (I hope) -- They work together. VERY WELL. >> >> I spent years on WebDNA. Besides Bob and Ken and a few others I would >> wager >> that have been on here as long as anyone. Long long long time :-) >> >> Truth is I still use DNA flat files. And I also use the table tag to >> temporarily store MSSQL data returns for recursive (RAM) searching. >> >> I use both. In the same page of code. And again, it works very very well >> :-) >> >> Why MSSQL? Well, there are lots of reasons. A few of them that come to >> mind >> are >> >> Transactional Logging. There have been times when we needed to go to >> backups >> and then rebuild all the data structure through time. Rare but it has >> happened. >> >> Multiple points of entry and exit. I use it in an environment where there >> are asp pages, php pages, Access Apps, and TPL pages and they all need to >> manipulate the same data in REAL TIME. And no the data dumping, >> import/exporting of data in bulk to be "semi-realtime" is not acceptable. >> With DNA/MSSQL this is a snap. How much extra code is needed for this? Um, >> none. >> >> True data warehousing as well as multiple front end servers hitting the >> same >> data. Across the network or across the web it all doable. Again in real >> time. >> >> >> Why MSSQL instead of MySQL? Well mostly because its a MS shop. Gotta work >> within the system. Frankly, if the tests all hold up it seems that the >> syntax is identical if you hit MySQL with ODBC instead of the Native DNA >> MySQL tags. Why is this so important? Well when your sitting there >> debugging >> and need to hit the SQL server with your search in Query Analyzer its a >> lot >> better when all you have to do is copy and paste your SQL tag which would >> not work with the native tags (best I can tell). >> >> Huge data sets DO suffer from the undefined nature of WebDNA tables. >> Anyone >> doing large text searches on the two can attest. It also suffers from no >> field definition when doing date searches and math. >> >> Lets not forget about the join context instead of recursive searching! The >> ability to group across multiple tables with doing recursive searching in >> a >> FI loop will start making a HUGE difference on large data sets. >> >> >> Don't get me wrong guys. I use WebDNA every single day for some pretty >> in-depth tools (one rolling out to schools across NY soon). For the most >> part now, we use DNA as the front end to MSSQL. We still do flat files >> resident in DNA, and also will be doing MySQL (through ODBC soon). So I >> don't see it as a either or. Integrating SQL tags was a critical maneuver >> on >> the part of SMSI... If only it had come with marketing ;-) >> >> >> >> >> >> >> On 4/3/06 11:12 PM, "Bob Minor"
wrote: >> >> >>> Good thinking, why don't they build all cars to handle pulling a load >>> like a tractor trailer I mean surely we will all need to pull a bunch >>> of stuff one day! Or hey why not build all cars like a porsche >>> carrera gt, I mean we are all going to need to go fast someday. That >>> is not to say that you don't build for the future but you don't put >>> money into something that may NEVER happen. You can build what you >>> want for a fraction of the cost so that you can one day rebuild when >>> you need to. You really think they built ebay from scratch the way it >>> is today, sorry it was an evolution. >>> >>> The right tool for the right job is the right thing! >>> >>> On Apr 3, 2006, at 5:58 PM, Adam O'Connor wrote: >>> >>> >>>> In this scenario, webcat would be quite distinguished. >>>> >>>> I know these examples are large, but really, if you are going to >>>> devote time and effort with a webdev platform, why not ensure it >>>> can handle what the others are capable of handling. >>>> >>> ------------------------------------------------------------- >>> This message is sent to you because you are subscribed to >>> the mailing list . >>> To unsubscribe, E-mail to: >>> To switch to the DIGEST mode, E-mail to >>> >>> Web Archive of this list is at: http://webdna.smithmicro.com/ >>> >> -- >> Alex J McCombie ~ Alex@Adventureskies.com p:315~233~9403 >> Adventure Skies Interactive (ASI) >> "You can find it all under Adventure Skies" >> >> >> >> >> >> >> ------------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> To switch to the DIGEST mode, E-mail to > digest@talk.smithmicro.com> >> Web Archive of this list is at: http://webdna.smithmicro.com/ >> > > > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > Web Archive of this list is at: http://webdna.smithmicro.com/ > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Well said. Have you found a way to use MySQL stored procedures with webcat? If so I would love to know, I can't wait to use them with webcat. nitai@computeroil.com wrote: > Let's put it in simple word: > > Once you start using SQL syntax and use some of the languages very own features like JOIN or UNION you simply won't go back to use flat files. > > Instead of using a search within a search and then a lookup within that founditems (all true real world examples) and you see how easy this is done with ONE SQL statement it should start making sense to everyone :-) > > It just open up a new world of possibilities. Imagine you have one single location for all your data and that location does not even has to be in house. That other systems can connect to it as well is a life saver sometimes. > > Now when you start with stored procedures you have another story where your database does all the work for you and not the webserver anymore... > > I don't think this is a conversation of the scripting language but more why to use SQL. > > Nitai > > -- > eContentPark - Enterprise Digital Asset Management > eServices - The complete SupportSuite > eSurvey - Online Questionnaire made easy > Redakto CMS - Content Management that simply works > > ComputerOil® AG > Neugutstrasse 66 > 8600 Dübendorf / Switzerland > Telefon +41 (0)844 44 55 66 > > info@computeroil.com > http://computeroil.com > > >> -----Original Message----- >> From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com] On Behalf Of >> Alex McCombie >> Sent: Dienstag, 4. April 2006 05:45 >> To: WebDNA Talk >> Subject: Re: Here we go again...WebDNA - SQL- Clustering >> >> Lol the funny thing everyone is so passionately debating the WebDNA tables >> VS. SQL like they are sworn enemies. >> >> Let me help (I hope) -- They work together. VERY WELL. >> >> I spent years on WebDNA. Besides Bob and Ken and a few others I would >> wager >> that have been on here as long as anyone. Long long long time :-) >> >> Truth is I still use DNA flat files. And I also use the table tag to >> temporarily store MSSQL data returns for recursive (RAM) searching. >> >> I use both. In the same page of code. And again, it works very very well >> :-) >> >> Why MSSQL? Well, there are lots of reasons. A few of them that come to >> mind >> are >> >> Transactional Logging. There have been times when we needed to go to >> backups >> and then rebuild all the data structure through time. Rare but it has >> happened. >> >> Multiple points of entry and exit. I use it in an environment where there >> are asp pages, php pages, Access Apps, and TPL pages and they all need to >> manipulate the same data in REAL TIME. And no the data dumping, >> import/exporting of data in bulk to be "semi-realtime" is not acceptable. >> With DNA/MSSQL this is a snap. How much extra code is needed for this? Um, >> none. >> >> True data warehousing as well as multiple front end servers hitting the >> same >> data. Across the network or across the web it all doable. Again in real >> time. >> >> >> Why MSSQL instead of MySQL? Well mostly because its a MS shop. Gotta work >> within the system. Frankly, if the tests all hold up it seems that the >> syntax is identical if you hit MySQL with ODBC instead of the Native DNA >> MySQL tags. Why is this so important? Well when your sitting there >> debugging >> and need to hit the SQL server with your search in Query Analyzer its a >> lot >> better when all you have to do is copy and paste your SQL tag which would >> not work with the native tags (best I can tell). >> >> Huge data sets DO suffer from the undefined nature of WebDNA tables. >> Anyone >> doing large text searches on the two can attest. It also suffers from no >> field definition when doing date searches and math. >> >> Lets not forget about the join context instead of recursive searching! The >> ability to group across multiple tables with doing recursive searching in >> a >> FI loop will start making a HUGE difference on large data sets. >> >> >> Don't get me wrong guys. I use WebDNA every single day for some pretty >> in-depth tools (one rolling out to schools across NY soon). For the most >> part now, we use DNA as the front end to MSSQL. We still do flat files >> resident in DNA, and also will be doing MySQL (through ODBC soon). So I >> don't see it as a either or. Integrating SQL tags was a critical maneuver >> on >> the part of SMSI... If only it had come with marketing ;-) >> >> >> >> >> >> >> On 4/3/06 11:12 PM, "Bob Minor" wrote: >> >> >>> Good thinking, why don't they build all cars to handle pulling a load >>> like a tractor trailer I mean surely we will all need to pull a bunch >>> of stuff one day! Or hey why not build all cars like a porsche >>> carrera gt, I mean we are all going to need to go fast someday. That >>> is not to say that you don't build for the future but you don't put >>> money into something that may NEVER happen. You can build what you >>> want for a fraction of the cost so that you can one day rebuild when >>> you need to. You really think they built ebay from scratch the way it >>> is today, sorry it was an evolution. >>> >>> The right tool for the right job is the right thing! >>> >>> On Apr 3, 2006, at 5:58 PM, Adam O'Connor wrote: >>> >>> >>>> In this scenario, webcat would be quite distinguished. >>>> >>>> I know these examples are large, but really, if you are going to >>>> devote time and effort with a webdev platform, why not ensure it >>>> can handle what the others are capable of handling. >>>> >>> ------------------------------------------------------------- >>> This message is sent to you because you are subscribed to >>> the mailing list . >>> To unsubscribe, E-mail to: >>> To switch to the DIGEST mode, E-mail to >>> >>> Web Archive of this list is at: http://webdna.smithmicro.com/ >>> >> -- >> Alex J McCombie ~ Alex@Adventureskies.com p:315~233~9403 >> Adventure Skies Interactive (ASI) >> "You can find it all under Adventure Skies" >> >> >> >> >> >> >> ------------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> To switch to the DIGEST mode, E-mail to > digest@talk.smithmicro.com> >> Web Archive of this list is at: http://webdna.smithmicro.com/ >> > > > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > Web Archive of this list is at: http://webdna.smithmicro.com/ > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Adam O'Connor
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Secured Order Forms (1998)
Why does setheader provide a db= parameter? (2005)
db creator (2000)
[movefile] create stationery files (1998)
Webcat and Sybase on OSX...anyone doing this currently? (2003)
Public beta 5 of WebCatalog 4.0 is now available (2000)
products db philosophy (2001)
hidden databases (2000)
WebCat2b15MacPlugin - showing [math] (1997)
WebCatalog Work (2001)
Looking up two prices in database? (1997)
Alternating colors (1997)
send mail problem? (1997)
WebCat2b15MacPlugin - showing [math] (1997)
Three new problems, maybe a fourth (1997)
form data submission gets truncated (1997)
multi-paragraph fields (1997)
[WebDNA] lighttpd.conf for php and webdna? (2013)
If Else Statement... (2004)
Empty Shopping Carts? (1998)