vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Our company is a service provider for scientific organizations, we host a lot of scientific sites, dynamic and static on LAMP. Now one of the users send me a zipped directory with *.frm, *.MYD and *.MYI files and asks me to place them in the MySQL directory. I have given him access to his database via PHPMyAdmin, I once convinced him to give me a file with SQL statements (tabel creates and data inserts), but no he persists on sending those *.MYD, *.frm and *.MYI files. Is this a normal way of working ? Are there any risks to copying that directory to /var/lib/mysql/ ? Risks as in malicious or just because of different mysql versions, ... ? thanx, J |
| ||||
| On Mon, 03 Dec 2007 08:54:39 +0100, Pugi! <puginews@gmail.com> wrote: > Our company is a service provider for scientific organizations, we > host a lot of scientific sites, dynamic and static on LAMP. > Now one of the users send me a zipped directory with *.frm, *.MYD and > *.MYI files and asks me to place them in the MySQL directory. > I have given him access to his database via PHPMyAdmin, I once > convinced him to give me a file with SQL statements (tabel creates and > data inserts), but no he persists on sending those *.MYD, *.frm and > *.MYI files. Is this a normal way of working ? Are there any risks to > copying that directory to /var/lib/mysql/ ? Risks as in malicious or > just because of different mysql versions, ... ? Yes, risks all around. Inform the user that this is not the way to do it, and might possibly break the entire database server. Every time this kind of action succeeds is actually more luck then anything else. It will normally sort of work depending on the actual data and similarities in database server (versions, setup, etc.), with absolutely no guarantee. Refer him to the manual (and mysqldump), and inform him or her that you will only be importing dumps into the database. If the client has it's own databaseserver/no other clients will feel the consequences, you can happily do as the client wishes, after you have warned him, and told him your hourly rate for fixing this if it goes haywire (and it no doubt will some day). This is offcourse not part of any normal service hours/contract, as you indicated what had to be done and the client explicitly stated he wanted to do this against all advice. -- Rik Wasmus |
| Thread Tools | |
| Display Modes | |
|
|