I am starting to do the R&D on the next phase of development on my program and I am looking for a database and I am wondering if MySQL Embedded is the solution.
The database needs to be embedded from the standpoint that when my application starts, so does the database, when mine shuts down, so does the database. The real key feature I am in need of is the physical database file to be able to be treated like any other datafile. Think of my software as job based. The user fires up my software, creates a new job, does his/her thing and exits. All the data, including the database file, for each job needs to exist in the job directory/folder so that later the user can copy the job folder to other locations. I know file base databases like MS Access are designed this way and I know databases like MS SQL are NOT. The MS SQL physical files cannot eaily be moved, or at least not the last time I check;) Will MySQL Embedded give me the ability I need to create a new physical database file for every job and load up older database jobs once the files are moved? Cartoper -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
