Re: [WebDNA] Use of MySQL with WebDNA

This WebDNA talk-list message is from

2010


It keeps the original formatting.
numero = 105818
interpreted = N
texte = Hi Chris! :-) I have not used MySQL (or other external db) outside of PHP (not yet with webdna), but I do not see how webdna's future can get around really strong support of that. Of course it is a royal pain to have to code outside of webdna's beautiful internal db system, but when the db's get too large, then it seems just too risky to not have options. Maybe in some cases it is not even just that webdna could not handle a large db, but that maybe their is just not enough RAM allotted in some setups. I have not read much of the articles around the current state of MySQL, but there is simply so much of it out there, that for all I know it is still the best option as backup format. (?) Maybe my very partial knowledge here will prove my lack of thorough familiarity with the range of server-side considerations, but at least it will add to getting discussion going. -Govinda On Sep 28, 2010, at 8:35 AM, christophe.billiottet@webdna.us wrote: > Good morning everyone! > > this email is for WebDNA users working with MySQL. We would like to > know how many of you need MySQL support and the reason why you > prefer using MySQL instead of the internal database system. > As you know, MySQL now belongs to Oracle with license restrictions > and we were thinking, in case external database support is > necessary, if a better/faster ODBC support woud not be a more > universal idea. We also gave SQLite a thought, but despite its > qualities, the internal WebDNA database system is more powerful. > > This is not a trivial matter, so we will listen to everyone. > > thank you! > > - chris--------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us ------------ Govinda govinda.webdnatalk@gmail.com Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Use of MySQL with WebDNA (Stuart Tremain 2010)
  2. RE: [WebDNA] Use of MySQL with WebDNA ("Dale Therio" 2010)
  3. Re: [WebDNA] Use of MySQL with WebDNA (Brian Fries 2010)
  4. Re: [WebDNA] Use of MySQL with WebDNA ("Mr. Robert Minor Jr." 2010)
  5. Re: [WebDNA] Use of MySQL with WebDNA (Kenneth Grome 2010)
  6. RE: [WebDNA] Use of MySQL with WebDNA ("Terry Nair" 2010)
  7. Re: [WebDNA] Use of MySQL with WebDNA (Paul Willis 2010)
  8. Re: [WebDNA] Use of MySQL with WebDNA (christophe.billiottet@webdna.us 2010)
  9. Re: [WebDNA] Use of MySQL with WebDNA (Paul Willis 2010)
  10. Re: [WebDNA] Use of MySQL with WebDNA (christophe.billiottet@webdna.us 2010)
  11. Re: [WebDNA] Use of MySQL with WebDNA (Govinda 2010)
  12. Re: [WebDNA] Use of MySQL with WebDNA (Toby Cox 2010)
  13. RE: [WebDNA] Use of MySQL with WebDNA ("Will Starck" 2010)
  14. Re: [WebDNA] Use of MySQL with WebDNA (Govinda 2010)
  15. Re: [WebDNA] Use of MySQL with WebDNA (Toby Cox 2010)
  16. [WebDNA] Use of MySQL with WebDNA (christophe.billiottet@webdna.us 2010)
Hi Chris! :-) I have not used MySQL (or other external db) outside of PHP (not yet with webdna), but I do not see how webdna's future can get around really strong support of that. Of course it is a royal pain to have to code outside of webdna's beautiful internal db system, but when the db's get too large, then it seems just too risky to not have options. Maybe in some cases it is not even just that webdna could not handle a large db, but that maybe their is just not enough RAM allotted in some setups. I have not read much of the articles around the current state of MySQL, but there is simply so much of it out there, that for all I know it is still the best option as backup format. (?) Maybe my very partial knowledge here will prove my lack of thorough familiarity with the range of server-side considerations, but at least it will add to getting discussion going. -Govinda On Sep 28, 2010, at 8:35 AM, christophe.billiottet@webdna.us wrote: > Good morning everyone! > > this email is for WebDNA users working with MySQL. We would like to > know how many of you need MySQL support and the reason why you > prefer using MySQL instead of the internal database system. > As you know, MySQL now belongs to Oracle with license restrictions > and we were thinking, in case external database support is > necessary, if a better/faster ODBC support woud not be a more > universal idea. We also gave SQLite a thought, but despite its > qualities, the internal WebDNA database system is more powerful. > > This is not a trivial matter, so we will listen to everyone. > > thank you! > > - chris--------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us ------------ Govinda govinda.webdnatalk@gmail.com Govinda

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:

Bug Fix for wbrk??? (1999) Performance Tuning (2006) if else problem (2003) CMS - Formatting Content (2004) Random tags HELP!!!! (1999) adding second sku (2000) Running _every_ page through WebCat ? (1997) [Sum] function? (1997) [tcp connect] (1998) international time (1997) Review comparison by PC Magazine: Open for On-line Business (1997) WebCatalog Hosting (1996) Processing all html files through WebCat or Typhoon (1998) WebCat2b15MacPlugin - [protect] (1997) [REPLACE] inside [FOUNDITEMS] (1998) POS (2000) Carrying Forward (1998) Date Help! (2003) More on the email templates (1997) [WebDNA] My SQL will not Connect (2020)