Re: [WebDNA] Use of MySQL with WebDNA
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 105820
interpreted = N
texte = I hadn't thought of this, but now that I think of it we also have a =problem with large, heavy traffic, heavy write DBsOn an ecommerce site we run, one particular db currently stands at =58,000 records (just over 1Mb) and it has started to corrupt records in =the last 4-6 months. Obviously this is something that tends not to =happen with MySQL.High traffic large databases with little writing do just fine, as do =high traffic smaller DBs with lots of writing. We have a record of all =dispatched items that gets written to just a few hundred times a day. =This stands at 167,000 records and 1.2Mb and is just fine.Meanwhile, with CakePHP and MySQL we have large DBs (250,000+) that are =written to 1,000+ times per day with no corruption.It's a problem that we can handle at the moment, by occasionally running =a first aid script, but I can't imagine that in 6-12 months we are going =to be running WebDNA in the same format as we do now.TCOn 28 Sep 2010, at 14:16, Govinda wrote:> Hi Chris! :-)>=20> 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. (?)>=20> 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.>=20> -Govinda>=20> On Sep 28, 2010, at 8:35 AM, christophe.billiottet@webdna.us wrote:>=20>> Good morning everyone!>>=20>> 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.>>=20>> This is not a trivial matter, so we will listen to everyone.>>=20>> thank you!>>=20>> - 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>=20> ------------> Govinda> govinda.webdnatalk@gmail.com>=20>=20>=20>=20> ---------------------------------------------------------> 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
Associated Messages, from the most recent to the oldest:
I hadn't thought of this, but now that I think of it we also have a =problem with large, heavy traffic, heavy write DBsOn an ecommerce site we run, one particular db currently stands at =58,000 records (just over 1Mb) and it has started to corrupt records in =the last 4-6 months. Obviously this is something that tends not to =happen with MySQL.High traffic large databases with little writing do just fine, as do =high traffic smaller DBs with lots of writing. We have a record of all =dispatched items that gets written to just a few hundred times a day. =This stands at 167,000 records and 1.2Mb and is just fine.Meanwhile, with CakePHP and MySQL we have large DBs (250,000+) that are =written to 1,000+ times per day with no corruption.It's a problem that we can handle at the moment, by occasionally running =a first aid script, but I can't imagine that in 6-12 months we are going =to be running WebDNA in the same format as we do now.TCOn 28 Sep 2010, at 14:16, Govinda wrote:> Hi Chris! :-)>=20> 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. (?)>=20> 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.>=20> -Govinda>=20> On Sep 28, 2010, at 8:35 AM, christophe.billiottet@webdna.us wrote:>=20>> Good morning everyone!>>=20>> 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.>>=20>> This is not a trivial matter, so we will listen to everyone.>>=20>> thank you!>>=20>> - 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>=20> ------------> Govinda> govinda.webdnatalk@gmail.com>=20>=20>=20>=20> ---------------------------------------------------------> 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
Toby Cox
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:
2.1b3 --> way slow (1997)
WebCat Contest Please Clarify (1998)
AOL access problems (1998)
SQL Madness (2005)
Help with Shipping Costs (1997)
WebCat2 - Getting to the browser's username/password data (1997)
OT: 800x600 (2003)
Why is my easy [AddLineItems] NOT working?? (2000)
Timer Values on [redirect] (1998)
Digest for 4/18/97 (1997)
Not really WebCat (1997)
WebCatalog for guestbook ? (1997)
[append] (1997)
Navigator 4.0 & tables (1997)
Emailer (1997)
Sum of [founditems] ? (2004)
color and size options / ARCHIVES (1997)
Practice runs ? (1997)
PCS Frames (1997)
Running 2 two WebCatalog.acgi's (1996)