On 03/04/2011 10:46 AM, Jerry Schwartz wrote:
-Original Message-
From: ed [mailto:eth...@earthlink.net]
[JS]
I guess wordwrap is going to mess this up;
mysql> show engines ;
[JS] Next time, try
SHOW ENGINES\G
Regards,
I see no differences. thanks for the rep
>-Original Message-
>From: ed [mailto:eth...@earthlink.net]
[JS]
>
>I guess wordwrap is going to mess this up;
>
>
>mysql> show engines ;
[JS] Next time, try
SHOW ENGINES\G
Regards,
Jerry Schwartz
Global Information Incorporated
195 Farmington Ave.
Farmington, CT 06032
860.674.8796 /
The biggest issue for me is that you want your development environment to be
as identical as possible to the production environment (to avoid mistakes when
you move your application over). You don't want your production environment to
accidentally access your development data; but at the same ti
Hi ed, all!
ed wrote:
> I have recently noticed I can not access a PHP application's data files,
> and the errors I am getting seem to show that a recent update of the
> distro (mandriva) no longer supports innodb, and this may be a reason
Which version were you using before, and which one are y
On Fri, Mar 4, 2011 at 1:32 AM, Angela liu wrote:
> Can Isolation levels be set per transaction? I know isolation levels can be
> set per session or globally, but not sure at transaction level.
Given that you can only have one transaction at a time in a session,
there is no real difference betw
I have recently noticed I can not access a PHP application's data files,
and the errors I am getting seem to show that a recent update of the
distro (mandriva) no longer supports innodb, and this may be a reason
(if this is not some sort of "catchall" error). I would like to know how
to add inn
Other people have answered with pros and cons of virtualisation, but I would
rather ask another question: why do you feel it necessary to split up the
database?
If it's only used for QC, it's probably not in intensive use. Why would you go
through the bother of splitting it up? You're staying
