![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
When I try to backup a table, as root, I get the following message: The storage engine for the table doesn't support backup How do I change this? |
#3
| |||
| |||
|
|
On Wed, 1 Dec 2010 14:52:35 -0800 (PST), bruce wrote: When I try to backup a table, as root, I get the following message: The storage engine for the table doesn't support backup How do I change this? Change what? The error message? Change that the storage engine doesn't support backup? Change what storage engine your table is using? |
#4
| |||
| |||
|
|
On Dec 1, 5:55 pm, "Peter H. Coffin"<hell... (AT) ninehells (DOT) com> wrote: On Wed, 1 Dec 2010 14:52:35 -0800 (PST), bruce wrote: When I try to backup a table, as root, I get the following message: The storage engine for the table doesn't support backup How do I change this? Change what? The error message? Change that the storage engine doesn't support backup? Change what storage engine your table is using? Peter's is the sort of reply that is not only unhelpful, it discourages people from asking questions in the first place. Bruce may not have provided enough information to adequately supply an answer, but the question itself is pretty clear: How does one backup tables when the engine cannot support the standard backup. At the very least, a reply that used common decency would be appreciated. To simply waste our time by being a jerk is not appreciated. I received the same error message when attempting to backup all tables that use the InnoDB engine. I found the answer here: http://dev.mysql.com/doc/refman/5.1/...up-policy.html. Hopefully this will point Bruce in the right direction. |
#5
| |||
| |||
|
|
On 12/6/2010 12:06 PM, Joel Finkel wrote: On Dec 1, 5:55 pm, "Peter H. Coffin"<hell... (AT) ninehells (DOT) com> *wrote: On Wed, 1 Dec 2010 14:52:35 -0800 (PST), bruce wrote: When I try to backup a table, as root, I get the following message: The storage engine for the table doesn't support backup How do I change this? Change what? The error message? Change that the storage engine doesn't support backup? Change what storage engine your table is using? Peter's is the sort of reply that is not only unhelpful, it discourages people from asking questions in the first place. *Bruce may not have provided enough information to adequately supply an answer, but the question itself is pretty clear: How does one backup tables when the engine cannot support the standard backup. At the very least, a reply that used common decency would be appreciated. *To simply waste our time by being a jerk is not appreciated. I received the same error message when attempting to backup all tables that use the InnoDB engine. I found the answer here: http://dev.mysql.com/doc/refman/5.1/...up-policy.html. *Hopefully this will point Bruce in the right direction. No, Peter's response is spot on. *Is your error message caused by the same problem the original op's was? *As there are a number of causes for this message, chances are very good you have an entirely different problem. Providing sufficient information at the start means we don't have to go back and continue asking more questions. See: http://www.catb.org/~esr/faqs/smart-questions.html -- ================== Remove the "x" from my email address Jerry Stuckle JDS Computer Training Corp. jstuck... (AT) attglobal (DOT) net ================== |
#6
| |||
| |||
|
|
On Dec 6, 12:39 pm, Jerry Stuckle<jstuck... (AT) attglobal (DOT) net> wrote: On 12/6/2010 12:06 PM, Joel Finkel wrote: On Dec 1, 5:55 pm, "Peter H. Coffin"<hell... (AT) ninehells (DOT) com> wrote: On Wed, 1 Dec 2010 14:52:35 -0800 (PST), bruce wrote: When I try to backup a table, as root, I get the following message: The storage engine for the table doesn't support backup How do I change this? Change what? The error message? Change that the storage engine doesn't support backup? Change what storage engine your table is using? Peter's is the sort of reply that is not only unhelpful, it discourages people from asking questions in the first place. Bruce may not have provided enough information to adequately supply an answer, but the question itself is pretty clear: How does one backup tables when the engine cannot support the standard backup. At the very least, a reply that used common decency would be appreciated. To simply waste our time by being a jerk is not appreciated. I received the same error message when attempting to backup all tables that use the InnoDB engine. I found the answer here: http://dev.mysql.com/doc/refman/5.1/...up-policy.html. Hopefully this will point Bruce in the right direction. No, Peter's response is spot on. Is your error message caused by the same problem the original op's was? As there are a number of causes for this message, chances are very good you have an entirely different problem. Providing sufficient information at the start means we don't have to go back and continue asking more questions. See: http://www.catb.org/~esr/faqs/smart-questions.html I do not want to start a flame war, but Peter's response was: "Change what? The error message? Change that the storage engine doesn't support backup?" Now, please, does anyone really think that Bruce wanted to change the error message? Does anyone seriously think that Bruce wanted to add backup support to the storage engine? Of course not. That sort of answer is read as it is intended: "You stupid twit, come back when you know what question to ask." It would have been helpful to explain that that error message can be caused by several things, and suggested specific things to look at. I am reminded of when I asked a question of the Rdb/VMS devos in 1985. Being one of the very first people to use that cutting-edge relational database in the field (and for a very large client and very real deadlines), I got a similar flip answer to an important question. A colleague of mine chastised the person who had basically told me to RTFM, and, 25 years later, I am thanking him in kind. /Joel Finkel Now I don't know but I've been told It's hard to run with the weight of gold Other hand I heard it said It's just as hard with the weight of lead - Robert Hunter top posting fixed |
#7
| |||
| |||
|
|
We are not your unpaid consultants |
#8
| |||
| |||
|
|
And if you're too lazy to RTFM, I would suggest you not come around here. We are not your unpaid consultants. |
#9
| ||||
| ||||
|
|
Jerry writes: And if you're too lazy to RTFM, I would suggest you not come around here. We are not your unpaid consultants. You fail to understand that this material is so vast and so complicated that many people do not even know how to find the proper documentation, how to use it, or know how to ask the proper question. Some people cannot understand the documentation, sometimes the documentation is inadequate, and, yes, sometimes it is wrong. |
|
In fact, groups like this ARE "staffed" by unpaid consultants. That is the POINT of groups like this. People give freely of their time and knowledge to those who need assistance. Does this give them license to be rude? I think not. |
|
But your suggestion is basically that people do not come around here to ask questions because you are not being paid to answer them. Thank you for letting us know who is, and is not, welcome here. Let the chochums talk amongst themselves. |
|
/Joel Finkel That's why if you please, I am on my bended knees, Bertha don't you come around here anymore. - Robert Hunter |
#10
| |||
| |||
|
|
I received the same error message when attempting to backup all tables that use the InnoDB engine. I found the answer here: http://dev.mysql.com/doc/refman/5.1/...up-policy.html. |
![]() |
| Thread Tools | |
| Display Modes | |
| |