Arg! This abomination 5.5 is causing more headaches,
postfix will not run, I've heard dovecot may not either, amongst others
postconf: /usr/lib/libmysqlclient.so.16: no version information
available (required by postcon
/etc/init.d/postfix start
* Starting Postfix Mail Transport Agent postfi
You need mysql-5.1 compat-libs package
or rebuild applications against 5.5
for feddora/rhel type "compat-mysql51" in google
there are packages from remi since he builds 5.5
this is nothing new and was the same with 5.1
while applications was linked against 5.0
Am 31.01.2011 09:24, schrieb Noel
On Mon, 2011-01-31 at 10:52 +0100, Reindl Harald wrote:
> You need mysql-5.1 compat-libs package
> or rebuild applications against 5.5
>
> for feddora/rhel type "compat-mysql51" in google
> there are packages from remi since he builds 5.5
>
> this is nothing new and was the same with 5.1
> while
Have you rebuilt all depending applications AFTER
rebuild of mysql 5.5?
BTW:
I also make my own source-builds with optimized flags but not dumb
configure & make, the better way is to build clean distro-packages
and install them with the package-manager, this way you would
get not installed the pac
On Mon, 2011-01-31 at 11:42 +0100, Reindl Harald wrote:
> Have you rebuilt all depending applications AFTER
> rebuild of mysql 5.5?
>
yes, built 5.5 a month ago, only today rebuilt postfix (upgraded 2.7.2
to 2.8.0)
This is a common problem, google fu indicates others have same problem,
some of
Hi!
I'm trying to create a InnoDB table.
CREATE TABLE `DATABASE`.`Teste2`(`id` SMALLINT(2) , `nome`
VARCHAR(10)) TYPE=InnoDB;
show table status from DATABASE like 'Teste2';
+++-++--++-+-+--+-
CREATE TABLE `DATABASE`.`Teste2`(`id` SMALLINT(2) , `nome`
VARCHAR(10)) ENGINE=InnoDB;
--
João Cândido de Souza Neto
""M. Rodrigo Monteiro"" escreveu na mensagem
news:AANLkTikv4dtLTh+BMqxCwcCw5K59PU5W=zrt3j3th...@mail.gmail.com...
Hi!
I'm trying to create a InnoDB table.
CREATE TABLE `DAT
Hi!
2011/1/31 João Cândido de Souza Neto :
> CREATE TABLE `DATABASE`.`Teste2`(`id` SMALLINT(2) , `nome`
> VARCHAR(10)) ENGINE=InnoDB;
>
I forget to put in the e-mail. I tryied with ENGINE and TYPE, samething.
Regards,
Rodrigo.
--
M. Rodrigo Monteiro
"Free as in Freedom, not free as in free
what does 'show create table teste2" shows
2011/1/31 João Cândido de Souza Neto
> Please, give us some information about your server.
>
> --
> João Cândido de Souza Neto
>
> ""M. Rodrigo Monteiro"" escreveu na mensagem
> news:AANLkTikw2rDzhZU2+SmVeiPnVCYB-Q=vce5nufa7o...@mail.gmail.com...
>
On Mon, Jan 31, 2011 at 09:39, Reindl Harald wrote:
> seems there is "skip-innodb" in your configuration
> what do "show engines;" say?
In my.cnf (comment)
#skip-innodb
mysql> show engines;
++-++--+--
Hi Monteiro,
Probably, InnoDB in not enabled by default on your MySQL server.
I guess the statement "show engines" can help you.
Please, strip "LEGAL ADVICE" from your subsequent messages to the list.
Thanks,
Rodrigo Ferreira
CMDEV, CMDBA, Msc.
--- On Mon, 1/31/11, M. Rodrigo Monteiro wrote:
'TYPE' is deprecated since long time ago and should be
replaced everywhere with 'ENGINE'
with mysql 5.5 'TYPE' is a hard error which can be problematic
if running statement-based replication with a 5.1 master
and 5.5 slave because the master writes the statement to
binlog and slave will stop repli
Am 31.01.2011 13:34, schrieb M. Rodrigo Monteiro:
> 2011/1/31 João Cândido de Souza Neto :
>> CREATE TABLE `DATABASE`.`Teste2`(`id` SMALLINT(2) , `nome`
>> VARCHAR(10)) ENGINE=InnoDB;
>>
>
> I forget to put in the e-mail. I tryied with ENGINE and TYPE, samething.
seems there is "skip-innodb"
I´m not so sure about that, but I think in MySql 3.23 the InnoDB engine was
disabled by default so you must be almost a PhD to enable it.
What about updating server?
--
João Cândido de Souza Neto
""M. Rodrigo Monteiro"" escreveu na mensagem
news:AANLkTimPVMS_e3dQyHS=bRyOy5WYp78hYhv6mN=2b.
Noel, all,
Noel Butler wrote:
> Arg! This abomination 5.5 is causing more headaches,
>
> postfix will not run, I've heard dovecot may not either, amongst others
>
>
> postconf: /usr/lib/libmysqlclient.so.16: no version information
> available (required by postcon
> /etc/init.d/postfix start
Hi Filipus, all!
Filipus Klutiero wrote:
> Hi,
> an international site has some content in several latin languages, for
> example English and French. Sometimes 2 pages, one in English and one in
> French, have the same name except for an accent (for example, in
> English, Demonstration, in French
Harald,
Reindl Harald wrote:
> You need mysql-5.1 compat-libs package
> or rebuild applications against 5.5
Your advice is correct in general, but not in this case:
1) Noel builds from source, as he writes later.
2) Both MySQL 5.1 and 5.5 come with version 16 of "libmysqlclient", so
an applic
2011/1/31 João Cândido de Souza Neto :
> I´m not so sure about that, but I think in MySql 3.23 the InnoDB engine was
> disabled by default so you must be almost a PhD to enable it.
But the version of MySQL is 5.1 as you can see below...
>
> What about updating server?
>
> # cat /etc/redhat-rel
Am 31.01.2011 19:31, schrieb Joerg Bruehe:
> 2) Both MySQL 5.1 and 5.5 come with version 16 of "libmysqlclient", so
>an application built against MySQL 5.1 can directly use that of 5.5
In theory!
Build a mysql 5.5 rpm for fedora 13 and install it
No way - Without the compat-package it will
Greetings All,
I am looking for a little help in setting a where clause.
I have a dateAdded field that is a DATETIME field.
I am looking to pull records from Midnight to midnight the previous day.
I thought just passing the date (without time) would get it but I keep
getting an empty record set.
S
On Monday 31 January 2011 21:12, Phillip Baker wrote:
> Greetings All,
>
> I am looking for a little help in setting a where clause.
> I have a dateAdded field that is a DATETIME field.
> I am looking to pull records from Midnight to midnight the previous day.
> I thought just passing the date (wit
Hi,
You should check your error logs for innodb errors, there will be the
key to the solution. If you want to avoid this behaviour, you can set
innodb=force in your configuration file to make innodb error fatal, or
set sql_mode to 'NO_ENGINE_SUBSTITUTION'.
Peter Boros
On 01/31/2011 08:21 PM
Thank you very much Jørn
Blessed Be
Phillip
"Never ascribe to malice what can be explained by incompetence"
-- Hanlon's Razor
On Mon, Jan 31, 2011 at 1:18 PM, Jørn Dahl-Stamnes
wrote:
> Jørn
On 1/31/2011 15:12, Phillip Baker wrote:
Greetings All,
I am looking for a little help in setting a where clause.
I have a dateAdded field that is a DATETIME field.
I am looking to pull records from Midnight to midnight the previous day.
I thought just passing the date (without time) would get i
On 01/31/2011 12:18 PM, Jørn Dahl-Stamnes wrote:
> On Monday 31 January 2011 21:12, Phillip Baker wrote:
>
>> Greetings All,
>>
>> I am looking for a little help in setting a where clause.
>> I have a dateAdded field that is a DATETIME field.
>> I am looking to pull records from Midnight to midn
I skimmed over this thread and I think I can help clarify the innodb,
rsync, and lvm situation.
The basic issue with just running rsync on the files under a running
mysqld is that the rsync
will copy different parts of files at different points in time. This
means that it could sync things
to disk
26 matches
Mail list logo
