Frank,
1) Check out the FEDERATED storage engine, that might help.
2) You cannot specify a different location for a read database and a
write database.
3) Another solution is to use multiple databases -- each database is
just a directory, so you could try to symlink:
ie, if your datadir is /var/lib/mysql, and the cd has the files at
/mnt/cdrom/dbfiles/,
then
ln -s /var/lib/mysql/dbname/ /mnt/cdrom/dbfiles
This method is not recommended, but it's a way to do it.
-Sheeri
On 4/7/06, Frank <[EMAIL PROTECTED]> wrote:
> Hi,
>
> is there a possibility to configure a MySQL database in such a way that I
> can store the database on a read-only medium (say a CD), but still be able
> to write to the database (without having to copy the datafiles to disk or
> memory first)?
>
> What I have in mind is something like telling MySQL to use a different
> datafile for the new data.
> Could partitioning come to the rescue? Although the documentation mentions
> that it is possible that partions reside in different physical locations
> ("Partitioning takes this notion a step further, by allowing you to
> distribute portions of individual tables across a filesystem according to
> rules which you can set largely as needed"), I could not find any
> description of how this could be done, or whether it has actually been
> implemented.
>
> The solution should work with either MyISAM or INNODB, or better still, be
> independent of the engine.
>
> Cheers,
> Frank
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
>
>
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
