Hello Victoria,
As far as I see bug of muliple log files still not fixed regardless
of last change in 4.0.4:
'FLUSH LOGS removed numerical extension for all future update logs.'
--
Best regards,
Artem mailto:[EMAIL PROTECTED]
sql query
Hello Victoria,
Thursday, August 15, 2002, you wrote:
AVR>> In case of repliacation circle (A->B->A) query 'flush log' on any of
AVR>> this servers create endless loop, with creating new binary log file
AVR>> on each iteration. (about 30 new files every second in my case)
> Thanks for bug r
Hello mysql,
In case of repliacation circle (A->B->A) query 'flush log' on any of
this servers create endless loop, with creating new binary log file
on each iteration. (about 30 new files every second in my case)
--
Best regards,
Artem mailto:[EMAIL PROTECTED]
Hello all,
I was check up 4.0.3 (from the Development Source Tree), bug still exist.
>>Description:
aor> I use replication circle (A->B, B->A) with 3.23.51 - all ok.
aor> But I got problem, when upgrade both my servers to 4.0.2.
aor> Mysqld create 30 new bin-log files eve
Hello Sergei,
Tuesday, July 23, 2002, 10:17:06 PM, you wrote:
SG> Hi!
SG> On Jul 23, Artem V. Ryabov wrote:
>> Hello mysql,
>>
>> see this 2 queries:
>> why they not equal?
>> why first skip many records?
>>
>> mysql> select left(ftTe
Hello Sergei,
Tuesday, July 23, 2002, 10:17:06 PM, you wrote:
SG> Hi!
SG> On Jul 23, Artem V. Ryabov wrote:
>> Hello mysql,
>>
>> see this 2 queries:
>> why they not equal?
>> why first skip many records?
>>
>> mysql> select left(ftTe
Hello mysql,
see this 2 queries:
why they not equal?
why first skip many records?
mysql> select left(ftText,20) from Txt_index where match(ftText)
against('+(wÝd200206*) +wÝ12p' in boolean mode);
+--+
| left(ftText,20) |
+--+
| wÝd20020601 wÝ12p
Hello developers,
What problem with release 4.0.2?
Why you can't release it also as 'alpha' and continue work on next
version like 4.0.3.
You alredy fix many bugs and add many very nice features,
such as query like 'MATCH ... AGAINST(... IN BOOLEAN MODE)'.
Release it!
We (users) wri
Hello mysql,
mysql> create temporary table _234 select -20020412051754 as b; select min(b) from
_234;
Query OK, 1 row affected (0.00 sec)
Records: 1 Duplicates: 0 Warnings: 0
+-+
| min(b) |
+-+
| -20020412051744 |
+-
Hello bugs,
min return not value from table.
mysql> select min(ord) from cSectText where SectID=932;
+-+
| min(ord)|
+-+
| -20020412051744 |
+-+
1 row in set (0.00 sec)
mysql> select ord from cSectText where SectID=932
Hello Jeremy,
Friday, January 25, 2002, 11:00:43 AM, you wrote:
>> Why query type
>>
>> select count(*) from table_name where key_field between 'min' and
>> 'max' so slow?
>>
>> example:
>>
>> mysql> select count(*) from Textes where ID between 7937 and 45061;
>> +--+
>> | count(*) |
>
Hello All,
When I use "order by .. DESC" in query, time always more then in
"order by .. ASC" case.
Explain say "Using filesort",in "DESC" case query.
Why???
Why I can't use key value in select like that:
select * from TableName where KEY(KEYNAME) select * from cSectText where SectID=1 o
12 matches
Mail list logo
