Re: Here we go again...

This WebDNA talk-list message is from

2006


It keeps the original formatting.
numero = 66702
interpreted = N
texte = Thanks for your kind words. Part of my background is instructor. So it = is important to clarify the definition and layout the facts. There are a lot more thoughts on selecting the database in both business = and technical sense. Flat file makes it too much hassle to do any = business intelligences, data mining or even reporting. It is not = scalable for enterprise application. -----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of Adam O'Connor Sent: Monday, April 03, 2006 3:16 PM To: WebDNA Talk Subject: Re: Here we go again... I agree. The fact that you can 'relationalize' web cat simply points=20 out that you are a talented scripter. Generally speaking sometimes tasks are best written with webcat's native = flat file db system. But in certain cases some of us find SQL a better=20 data system, due to its accessibility, reliability, and capacity among=20 other things.=20 I don't see the need to take a side on which is better, all depends what = you are using it for. Although I do lean more towards the SQL. Quite=20 frankly it is simple to use, so why not take advantage and blend your=20 proprietary knowledge with an industry-wide technology - in the end you=20 have benefited by broadening your skill set by learning to use an=20 industry standard data management system. Afterall, by implementing SQL=20 into your webdna webapps, you may get more out of webdna. Bess Ho wrote: > It is important to clarify these things to other WebDNA developers so = that they can be wiser in selecting database type to start their = project. > > -----Original Message----- > From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of > Donovan Brooke > Sent: Monday, April 03, 2006 2:20 PM > To: WebDNA Talk > Subject: Re: Here we go again... > > > Bess Ho wrote: > > =20 >> Thanks Kenneth. Thanks for clarifying the myth. >> >> I think it is important for developers to understand the facts.=20 >> =20 > > WebDNA is not "relational" database. By database definition, > > you must meet certain criteria to call something "relational" = database. > =20 >> MS Access is not a true database because it didn't meet all the = criteria. >> >> Bess >> =20 > > > Sure it is. > If you have data in one text file database that effects another = database's > records when edited.. you've essentially created a relational = database. Now, > there are deeper and darker "definitions" of how data is saved / = manipulated.. > but creating a relational database framework in webdna is not advanced = and it > is just as secure. > > Donovan > > > > > > > > > =20 ------------------------------------------------------------- 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:

    
  1. Re: Here we go again... ( "Bess Ho" 2006)
  2. Re: Here we go again... ( Kenneth Grome 2006)
  3. Re: Here we go again... ( "sal danna" 2006)
  4. Re: Here we go again... ( "Bess Ho" 2006)
  5. Re: Here we go again... ( Kenneth Grome 2006)
  6. Re: Here we go again... ( "Bess Ho" 2006)
  7. Re: Here we go again...WebDNA - SQL- Clustering ( Kenneth Grome 2006)
  8. Re: Here we go again...WebDNA - SQL- Clustering ( "Bess Ho" 2006)
  9. Re: Here we go again...WebDNA - SQL- Clustering ( Donovan Brooke 2006)
  10. Re: Here we go again...WebDNA - SQL- Clustering ( "Bess Ho" 2006)
  11. Re: Here we go again...WebDNA - SQL- Clustering ( "Bess Ho" 2006)
  12. Re: Here we go again...WebDNA - SQL- Clustering ( Alex McCombie 2006)
  13. Re: Here we go again...WebDNA - SQL- Stored Procedures ( Alex McCombie 2006)
  14. Re: Here we go again...WebDNA - SQL- Clustering ( Donovan Brooke 2006)
  15. Re: Here we go again...WebDNA - SQL- Clustering ( Donovan Brooke 2006)
  16. Re: Here we go again...WebDNA - SQL- Clustering ( Adam O'Connor 2006)
  17. Re: Here we go again...WebDNA - SQL- Clustering ( nitai@computeroil.com 2006)
  18. Re: Here we go again...WebDNA - SQL- Clustering ( Donovan Brooke 2006)
  19. Re: Here we go again...WebDNA - SQL- Clustering ( Alex McCombie 2006)
  20. Re: Here we go again...WebDNA - SQL- Stored Procedures ( Adam O'Connor 2006)
  21. Re: Here we go again...WebDNA - SQL- Clustering ( nitai@computeroil.com 2006)
  22. Re: Here we go again... ( nitai@computeroil.com 2006)
  23. Re: Here we go again... ( Kenneth Grome 2006)
  24. Re: Here we go again...WebDNA - SQL- Clustering ( Donovan Brooke 2006)
  25. Re: Here we go again... ( Donovan Brooke 2006)
  26. Re: Here we go again...WebDNA - SQL- Clustering ( Alex McCombie 2006)
  27. Re: Here we go again... ( Kenneth Grome 2006)
  28. Re: Here we go again...WebDNA - SQL- Clustering ( Bob Minor 2006)
  29. Re: Here we go again... ( "Bess Ho" 2006)
  30. Re: Here we go again... ( "Bess Ho" 2006)
  31. Re: Here we go again... ( Donovan Brooke 2006)
  32. Re: Here we go again...WebDNA - SQL- Clustering ( Stuart Tremain 2006)
  33. Re: Here we go again...WebDNA - SQL- Clustering ( Adam O'Connor 2006)
  34. Re: Here we go again... ( "Bess Ho" 2006)
  35. Re: Here we go again... ( Adam O'Connor 2006)
  36. Re: Here we go again... ( Adam O'Connor 2006)
  37. Re: Here we go again... ( Marc Thompson 2006)
  38. Re: Here we go again... ( "Bess Ho" 2006)
  39. Re: Here we go again... ( "Bess Ho" 2006)
  40. Re: Here we go again... ( Donovan Brooke 2006)
  41. Re: Here we go again... ( Adam O'Connor 2006)
  42. Re: Here we go again... ( "Bess Ho" 2006)
  43. Re: Here we go again... ( "Bess Ho" 2006)
  44. Re: Here we go again... ( Pat McCormick 2006)
  45. Re: Here we go again... ( Pat McCormick 2006)
  46. Re: Here we go again... ( "Bess Ho" 2006)
  47. Re: Here we go again... ( "Bess Ho" 2006)
  48. Re: Here we go again... ( Pat McCormick 2006)
  49. Re: Here we go again... ( Chris 2006)
  50. Re: Here we go again... ( Terry Wilson 2006)
  51. Re: Here we go again... ( Donovan Brooke 2006)
  52. Re: Here we go again... ( Donovan Brooke 2006)
  53. Re: Here we go again... ( Adam O'Connor 2006)
  54. Re: Here we go again... ( Kenneth Grome 2006)
  55. Re: Here we go again... ( Kenneth Grome 2006)
  56. Re: Here we go again... ( "Dan Strong" 2006)
  57. Re: Here we go again... ( "Dan Strong" 2006)
  58. Re: Here we go again... ( Donovan Brooke 2006)
  59. Re: Here we go again... ( Adam O'Connor 2006)
  60. Re: Here we go again... ( Donovan Brooke 2006)
  61. Re: Here we go again... ( Pat McCormick 2006)
  62. Re: Here we go again... was: DDEConnect not working ( Robie Blair 2006)
  63. Re: Here we go again... ( "Bess Ho" 2006)
  64. Re: Here we go again... ( Kenneth Grome 2006)
  65. Re: Here we go again... ( Terry Wilson 2006)
  66. Re: Here we go again... ( Larry Hewitt 2006)
  67. Re: Here we go again... ( Phil Herring 2006)
  68. Re: Here we go again... ( Jesse Proudman 2006)
  69. Re: Here we go again... ( Stuart Tremain 2006)
  70. Re: Here we go again... ( Jesse Proudman 2006)
  71. Re: Here we go again... ( Stuart Tremain 2006)
  72. Re: Here we go again... ( Jesse Proudman 2006)
  73. Re: Here we go again... ( "Dan Strong" 2006)
  74. Re: Here we go again... ( Jesse Proudman 2006)
  75. Re: Here we go again... ( "Dan Strong" 2006)
  76. Re: Here we go again... ( Stuart Tremain 2006)
  77. Re: Here we go again... was: DDEConnect not working ( Chris 2006)
  78. Re: Here we go again... was: DDEConnect not working ( Kenneth Grome 2006)
  79. Re: Here we go again... was: DDEConnect not working ( Chris 2006)
  80. Re: Here we go again... was: DDEConnect not working ( Kenneth Grome 2006)
  81. Re: Here we go again... was: DDEConnect not working ( Chris 2006)
  82. Re: Here we go again... was: DDEConnect not working ( Kenneth Grome 2006)
  83. Re: Here we go again... ( Donovan Brooke 2006)
  84. Re: Here we go again... was: DDEConnect not working ( Chris 2006)
  85. Re: Here we go again... ( Terry Wilson 2006)
  86. Re: Here we go again... was: DDEConnect not working ( Kenneth Grome 2006)
  87. Re: Here we go again... was: DDEConnect not working ( Stuart Tremain 2006)
  88. Re: Here we go again... was: DDEConnect not working ( "Dan Strong" 2006)
  89. Re: Here we go again... was: DDEConnect not working ( Stuart Tremain 2006)
  90. Re: Here we go again... was: DDEConnect not working ( Jay Van Vark 2006)
  91. Re: Here we go again... was: DDEConnect not working ( Stuart Tremain 2006)
  92. Re: Here we go again... was: DDEConnect not working ( "Bess Ho" 2006)
  93. Re: Here we go again... was: DDEConnect not working ( Gary Krockover 2006)
  94. Here we go again... was: DDEConnect not working ( "Dan Strong" 2006)
Thanks for your kind words. Part of my background is instructor. So it = is important to clarify the definition and layout the facts. There are a lot more thoughts on selecting the database in both business = and technical sense. Flat file makes it too much hassle to do any = business intelligences, data mining or even reporting. It is not = scalable for enterprise application. -----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of Adam O'Connor Sent: Monday, April 03, 2006 3:16 PM To: WebDNA Talk Subject: Re: Here we go again... I agree. The fact that you can 'relationalize' web cat simply points=20 out that you are a talented scripter. Generally speaking sometimes tasks are best written with webcat's native = flat file db system. But in certain cases some of us find SQL a better=20 data system, due to its accessibility, reliability, and capacity among=20 other things.=20 I don't see the need to take a side on which is better, all depends what = you are using it for. Although I do lean more towards the SQL. Quite=20 frankly it is simple to use, so why not take advantage and blend your=20 proprietary knowledge with an industry-wide technology - in the end you=20 have benefited by broadening your skill set by learning to use an=20 industry standard data management system. Afterall, by implementing SQL=20 into your webdna webapps, you may get more out of webdna. Bess Ho wrote: > It is important to clarify these things to other WebDNA developers so = that they can be wiser in selecting database type to start their = project. > > -----Original Message----- > From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of > Donovan Brooke > Sent: Monday, April 03, 2006 2:20 PM > To: WebDNA Talk > Subject: Re: Here we go again... > > > Bess Ho wrote: > > =20 >> Thanks Kenneth. Thanks for clarifying the myth. >> >> I think it is important for developers to understand the facts.=20 >> =20 > > WebDNA is not "relational" database. By database definition, > > you must meet certain criteria to call something "relational" = database. > =20 >> MS Access is not a true database because it didn't meet all the = criteria. >> >> Bess >> =20 > > > Sure it is. > If you have data in one text file database that effects another = database's > records when edited.. you've essentially created a relational = database. Now, > there are deeper and darker "definitions" of how data is saved / = manipulated.. > but creating a relational database framework in webdna is not advanced = and it > is just as secure. > > Donovan > > > > > > > > > =20 ------------------------------------------------------------- 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/ "Bess Ho"

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:

WebCatalog2 Feature Feedback (1996) Encrypt question. (2000) AOL and webcat (1998) [Sum] function? (1997) formula.db, adding option prices (1997) Introduction/Tutorial/QuickStart (1997) 2.0 Beta (1997) [showif]'s inside [search] params? (2000) verify online (1997) Reversed words (1997) test (2002) Hiding a character (2001) [WebDNA] HTML5 (2010) OLD ORDERS (1998) [BULK] [WebDNA] WebDNA Code and HTML WYSIWYG Editors (2011) Ampersand (1997) PIXO with cometsite ... and/or other plugins (1998) Triggers (1999) Mime Headers for Mail (1998) syntax question, not in online refernce (1997)