Re: mysql Digest 12 Aug 2015 13:08:20 -0000 Issue 5317

2015-08-12 Thread hsv
On 2015/08/12 10:49, Bob Eby wrote: converting from MyISAM to innodb would certainly pose problems, I guess the main question would be is MyISAM functionality a strict sub-set of innodb? I'm not sure, but maybe someone else here knows better. No, as already said: for one thing, MyISAM allows mor

Re: table desin question

2015-08-12 Thread hsv
On 2015/08/12 09:42, Johan De Meersman wrote: - Original Message - >From: "Richard Reina" >Subject: table desin question > >Would this be the best way to design the schema and would it be best to >make the client ID and technician ID the same as the user ID as they relate >to the same pe

Re: mysql Digest 12 Aug 2015 13:08:20 -0000 Issue 5317

2015-08-12 Thread Reindl Harald
Am 12.08.2015 um 16:49 schrieb Bob Eby: converting from MyISAM to innodb would certainly pose problems, I guess the main question would be is MyISAM functionality a strict sub-set of innodb? I'm not sure, but maybe someone else here knows better no it is for sure not signature.asc Descri

Re: mysql Digest 12 Aug 2015 13:08:20 -0000 Issue 5317

2015-08-12 Thread Bob Eby
converting from MyISAM to innodb would certainly pose problems, I guess the main question would be is MyISAM functionality a strict sub-set of innodb? I'm not sure, but maybe someone else here knows better. Good luck, Robert -- MySQL General Mailing List For list archives: http://lists.mysql.co

Re: table desin question

2015-08-12 Thread Johan De Meersman
- Original Message - > From: "Richard Reina" > Subject: table desin question > > Would this be the best way to design the schema and would it be best to > make the client ID and technician ID the same as the user ID as they relate > to the same person? Close enough; but I think it would

Re: Changing storage engine in dump file.

2015-08-12 Thread Pothanaboyina Trimurthy
it is better to take the dump as it is on the master, restore it on the salve and then change the storage engine through alter table commands that will be the right way of doing and you could see any issues while converting from MyISAM to InnoDB. On Wed, Aug 12, 2015 at 6:51 PM, Johan De Meersman

Re: Changing storage engine in dump file.

2015-08-12 Thread Reindl Harald
Am 12.08.2015 um 15:07 schrieb geetanjali mehra: I am in the process of creating a new slave. On my master, there is a mix of innodb and myisam tables. I want all my tables to be created in innodb on slave. I have planned to change the value of storage engine from innodb to myisam in dump file

table desin question

2015-08-12 Thread Richard Reina
I am ceating a database application with two different types of users, clients and technicians. Both types of users have to create and account in which they become "users". From there they can become clients or technicians or perhaps even both. Since each type describe different attributes -- use

Re: Changing storage engine in dump file.

2015-08-12 Thread Johan De Meersman
- Original Message - > From: "geetanjali mehra" > Subject: Changing storage engine in dump file. > > Is there any implications in doing so. Is this approach correct? Will I > face any problem in syncing the slave? The first thing that occurs to me, is that the maximum key lenght for MyI

Changing storage engine in dump file.

2015-08-12 Thread geetanjali mehra
Hi, I am in the process of creating a new slave. On my master, there is a mix of innodb and myisam tables. I want all my tables to be created in innodb on slave. I have planned to change the value of storage engine from innodb to myisam in dump file itself using sed . Running that dump file on t