Re: Here we go again...WebDNA - SQL- Clustering
This WebDNA talk-list message is from 2006
It keeps the original formatting.
numero = 66735
interpreted = N
texte = Sorry to beat a dead horse but I think its good this topic is being discussed. SQL is a skill, and should be added to your skill set. Skills should be added to your resume not words. For some adding SQL to their skill set would be advantageous at getting a position or meeting a clients specs for a project -nothing wrong with that. If there are clients reading this then I think they should see that webdna is a nice webdev scripting language which can be keenly worked to perform well in many situations by talented developers. Further, they should know that webdna has the capability to utilize complex database systems used across the industry. Donovan Brooke wrote: > 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 > > This was a conversation about SMSI support that turned into (false) > statements about webdna that turned into SQL promotion (amongst other > things). :-) I was > correcting wreckless false statements such as webdna db's not > being relationable, and more generally, the message that webdna > is not a valid solution. Frankly, I'm a bit suprised that no other > long-timers joined in. > > > I don't know when the conversation turned into promoting SQL, but you > can count me in. I am not against using the right tool for the > job. But I think using SQL because its accepted or using SQL for your > resume is just that.. using it for the resume. Though I have used the SQL > tags in the very occassional soution, relational flat files > still are the best working solution for 97% of my clients (I do mostly > eCommerce stuff). There is absolutely no downside to using them. The > times I do consider other options is when the customer wants to connect > to a core inventory database or something.. or even when they are > thinking about connections in the future... > Flat files can migrate to most any platform.. so even if webdna > dissappears, the data is just fine (well, webdna encrypted fields would > have to be parsed). > > I said that I think it's wreckless.. because end users (our clients) may > watch this list. They are getting false ideas about webdna's > capabilities. > > Donovan > ------------------------------------------------------------- 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:
Sorry to beat a dead horse but I think its good this topic is being discussed. SQL is a skill, and should be added to your skill set. Skills should be added to your resume not words. For some adding SQL to their skill set would be advantageous at getting a position or meeting a clients specs for a project -nothing wrong with that. If there are clients reading this then I think they should see that webdna is a nice webdev scripting language which can be keenly worked to perform well in many situations by talented developers. Further, they should know that webdna has the capability to utilize complex database systems used across the industry. Donovan Brooke wrote: > 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 > > This was a conversation about SMSI support that turned into (false) > statements about webdna that turned into SQL promotion (amongst other > things). :-) I was > correcting wreckless false statements such as webdna db's not > being relationable, and more generally, the message that webdna > is not a valid solution. Frankly, I'm a bit suprised that no other > long-timers joined in. > > > I don't know when the conversation turned into promoting SQL, but you > can count me in. I am not against using the right tool for the > job. But I think using SQL because its accepted or using SQL for your > resume is just that.. using it for the resume. Though I have used the SQL > tags in the very occassional soution, relational flat files > still are the best working solution for 97% of my clients (I do mostly > eCommerce stuff). There is absolutely no downside to using them. The > times I do consider other options is when the customer wants to connect > to a core inventory database or something.. or even when they are > thinking about connections in the future... > Flat files can migrate to most any platform.. so even if webdna > dissappears, the data is just fine (well, webdna encrypted fields would > have to be parsed). > > I said that I think it's wreckless.. because end users (our clients) may > watch this list. They are getting false ideas about webdna's > capabilities. > > Donovan > ------------------------------------------------------------- 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:
problems with 2 tags (1997)
Shipping formula problem (1997)
search context w shownext works! (1997)
Not really WebCat (1997)
5.0 tips etc (2003)
Freeze (2003)
[Replace] (2000)
Couple of techno questions (1999)
SetHeader (1999)
searchable list archive (1997)
Practice runs ? (1997)
[SHOWNEXT] Examples (1997)
Bug Report, maybe (1997)
Can ShowNext do this? SOLVED (2000)
Protecting webdelivery (1997)
Dynamic Generation of PDFs? (2003)
frustrated with search (2001)
MasterCounter and capitalization (1997)
search double negative comparison (2001)
prev & Next commands (1999)