I use it for help entries atm. Later on, I plan on moving whole entire areas over to the database. This will allow several things. 1) More reliability readability 2) Easier to update on the mud w/o a copyover 3) My Offline Editor I'm coding up will be able to have "direct" access to the area files which will enable imediate updating of the mud. 4) When something is edited, you won't have to reload the entire area file, just reload the data on that one thing instead. So in the long run, amount of time it takes to do a change will have increased. And just like when someone "does" do a regular copyover, when a player logs in they will still have to do a remove all wear all routine, unless, since we may move pfiles as well as u mentioned, we can just query the database and update things there w/o them even loggin on. :)
All in good time, tho. all in good time. First, MySQL needs to incorporate linking tables. Which, as far as I know, they do not do at this time. Rheede ----- Original Message ----- From: "Jason Gauthier" <[EMAIL PROTECTED]> To: "'Angel of Death'" <[EMAIL PROTECTED]>; <[email protected]> Sent: Sunday, March 31, 2002 11:00 PM Subject: RE: MYSQL > I think someone here used it to store helpfiles. And i think Kyndig is > programming an SQL mud (wrong person?) > > But, personally, I've done extensive mysql development when I changed a BBS > to use it. > I don't know that I see much benefit of using it with ROM, with the > exception of a bit more reliable pfile saving.
