Converting DBF databases to mySQL

[robinemcd]

We have a non-merchant application written in MIVA Script. The database is using DBF files and we are looking to upgrade them to mySQL. We are trying to understand the process to make this upgrade. Is there documentation that someone can point us to in how to do this within a Miva context?

One thing that is unique to our databases is that each of our customers has their own database of files that sit in it's own directory, assuring that their data is not co-mingled with other customers' data and we need to keep that structure. We are unsure of how that would work with a mySQL database.

Clearly we are at the infancy of this project, but are hoping to get pointed in the right direction. Thanks in advance.

[ILoveHostasaurus]

You would normally do this as a pull/push with a standalone conversion script, iterating through records in the dbf files using the dbf functions, and inserting them into the corresponding SQL-based target using those appropriate queries. Highly recommend only using prepared statements, to avoid sql injection and similar attack vectors. You would definitely not place each customer's data into a unique database in the relational database world; there's really nothing gained by doing that, in either scenario. If your application is compromised, it's going to have access to all the data regardless of whether it's been separated into unique dbf's or unique mysql databases. However, at least with SQL your data is no longer also at risk from filesystem access, like it would be if it was in dbf files and someone compromises your FTPS/SSH credentials.