select IF(BOOK1PL,BOOK1PL,BOOK1EN)
from tBooksextra where ksi='id'
- (content of BOOK1EN)
select BOOK1PL from tBooksextra
WHERE BOOK1PL IS NOT NULL
AND BOOK1PL!='' AND ksi='id'
- (content of BOOK1PL).
Why didn't I get the content of BOOK1PL in 1st query?
(checked in 4.0.21 and 4.1.7)
./
SELECT TYTUL FROM tKsidata
WHERE MATCH (TYTUL) AGAINST (space)
ORDER BY TYTUL
TYTUL
Shaping Space 2ed
National Air Space Museum
Light Space
Free Space Architecture
Does Economics Space Matter ?
Economies of Signs Space
Industry Space Competition Contribution of Economists of P
Przemyslaw Popielarski [EMAIL PROTECTED] wrote:
SELECT TYTUL FROM tKsidata
WHERE MATCH (TYTUL) AGAINST (space)
ORDER BY TYTUL
TYTUL
Shaping Space 2ed
National Air Space Museum
Light Space
Free Space Architecture
Does Economics Space Matter ?
[...]
...and compiling own binary from
Sasha Pachev [EMAIL PROTECTED] wrote:
Check if you have any replication restricting rules on the slave.
There might be a bug that incorrectly flags a query to be excluded.
If that is the case, then try to re-write the rules to see if you can
get around the bug.
Yes. I have recently add the
SELECT TYTUL FROM tKsidata
WHERE MATCH (TYTUL) AGAINST (space)
ORDER BY TYTUL
TYTUL
Shaping Space 2ed
National Air Space Museum
Light Space
Free Space Architecture
Does Economics Space Matter ?
Economies of Signs Space
Industry Space Competition Contribution of Economists of P
Money Space
I'm executing on master a long and complicated query such:
UPDATE (lots of tables, lots of LEFT JOIN) SET ... WHERE .
The query updates i.e. 3816 rows.
The query DOES replicate do master's and slave's binary log.
But it DOES NOT execute on slave. 3816 rows are not updated on slave
and slave
I'm executing on master a long and complicated query such:
UPDATE (lots of tables, lots of LEFT JOIN) SET ... WHERE .
Okey, I simplified the query to:
-
UPDATE
tKsidata,
tKsiabeksiazki
SET
tKsidata.STAN_REALNY=tKsiabeksiazki.STAN
WHERE
tKsidata.ksi='0815120877' and
This is the first 4.1 production release.
What about MyODBC 3.52 / 3.53 / whatever compatible with MySQL 4.1?
--
./ premax
./ [EMAIL PROTECTED]
./ koniec i bomba, a kto czytal ten traba. w.g.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
User variables do not work with REGEXP under MySQL 4.0.21 4.1.5.
Is this a bug or a feature?
--
./ premax
./ [EMAIL PROTECTED]
./ koniec i bomba, a kto czytal ten traba. w.g.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
Paul DuBois [EMAIL PROTECTED] wrote:
User variables do not work with REGEXP under MySQL 4.0.21 4.1.5.
Is this a bug or a feature?
It's difficult to provide an answer to this because you're providing
no information about what do not work means. Can you be more
specific?
Sure. I didn't
Paul DuBois [EMAIL PROTECTED] wrote:
SELECT
@a:=FIRMLEGALZIPCODE
FROM tCustomers
WHERE @a REGEXP [0-9]
- Empty set (0.03 sec)
You're expecting the value to be selected first so that you then can
test it with the WHERE clause later.
Of course you're right. Thanks. According to your
Hickey,Thom [EMAIL PROTECTED] wrote:
One thing that 4.1 is better at is speeding up repeated queries,
...thanks to query cache, introduced in 4.0.1.
so
for testing we're forced to run thousands of queries through the
system to avoid speed-ups across runs.
SELECT SQL_NO_CACHE is pretty
I've got two Linux x86 servers: master and slave, both with MySQL 4.0.20
from the same package. On the master I do:
SET CHARACTER SET cp1250_latin2;
UPDATE `my_tab` SET `my_field`='my_cp1250_string';
and got this in both master's and slave's log.
On master the data is properly translated into
Jeremy March wrote:
I think --with-extra-charsets=none means that no additional character
sets will be _compiled_ into the server. Complex character sets must be
compiled into MySQL, but simple ones can be loaded dynamically. I think
the character sets you are seeing are ones that can be
Egor Egorov wrote:
Why do I still get all these character sets and how to get rid of them ?
If you want to have only latin1 configure MySQL with --with-charset=latin1
option,
additional character sets you can define with --with-extra-charsets
option.
This was the first what I did. And the
I'm trying to build MySQL 4.0.18 for Linux x86 2.4.24 from source without
support for extra charsets. Lets say I need only latin1.
My configure:
FLAGS=-O3 -march=pentium4 -mcpu=pentium4 -fomit-frame-pointer CXX=gcc
CXXFLAGS=-O3 -march=pentium4 -mcpu=pentium4 -felide-constructors
-fno-exceptions
Keith Spiller wrote:
I am trying to figure out how to use the NOW() function with a MySQL
Insert command on a Timestamp field.
Okey, either use NOW() on the DATETIME field, or use TIMESTAMP field
without inserting there value.
Here is my mysql command:
INSERT INTO $tablename
(sender,
I reconfigured and recompiled MySQL 3.23.53 that is supports now conversion
between Windows-1250 and ISO-8859-2 charsets.
If I do 'set character set cp1250_latin2' in a session, then everything goes
all right BUT only in insert/update/select statements.
If I do the same set and use LOAD DATA
Jack Chen wrote:
$ mysqladmin -u root password PASSWORD
mysqladmin: connect to server at 'localhost' failed
error: 'Access denied for user: 'root@localhost' (Using password: NO)'
Could you inform me why?
That's why:
$ mysqladmin -uroot -pyourpassword PASSWORD newpassword
--
./ premax
./
I'm using mysql Ver 11.16 Distrib 3.23.49, for slackware-linux-gnu (i386).
Everything was just fine for months, but yeasterday I started to use one of
the tables by connecting to it with MS Access 2000. The table has ~10
records. And the strange thing: it was working for few hours
Remy Dufour [EMAIL PROTECTED] wrote:
Anyone here got a hint about release date of My sql version 4.1 ?
It was metioned on the mysql-bugs list today:
Alpha version of 4.1 should come out this year.
-- Mr. Sinisa Milivojevic [EMAIL PROTECTED]
--
./ premax
./ [EMAIL PROTECTED]
./ koniec i
Sergei Golubchik [EMAIL PROTECTED] wrote:
1 row in set (0.00 sec)
Works fine for me (that is No rows - and no bug).
Probably, it's one of numerous fulltext-related bugs that were fixed
since 4.0.1 release.
Will you fix it in 3.23.x ? There is still lot of time (I think) to
release 4.x
Sergei Golubchik [EMAIL PROTECTED] wrote:
It looks like a bug. Can you create a test case for this ?
create table tBooks (
isbn char(10) not null primary key,
title varchar(60) not null,
fulltext index (title)
);
insert into tBooks (isbn,title) values
('1876340436','2000 Lonely Planet
SELECT ISBN,TITLE FROM tBooks
WHERE tBooks.ISBN=1876340436
AND MATCH (tBooks.TITLE) AGAINST (britannica)
++-+
| ISBN | TITLE |
++-+
| 1876340436 | 2000 Lonely Planet Calendar |
3.23.50 not yet published, but 3.23.51 is already being developed, according
to the manual at http://www.mysql.com/doc/N/e/News-3.23.51.html.
--
./ premax
./ [EMAIL PROTECTED]
-
Before posting, please check:
I've tried to export some data from my MySQL database (3.23.49) using
mysqldump -X to a XML file.
And I've got something like that:
?xml version=1.0?
tKsidata
KSI1572160047KSI
TYTULAmerican Gothic CookbookTYTUL
WYDppressWYD
ROK0/ROK
NRW0/NRW
STRON0/STRON
ISBN1-57216-004-7ISBN
Hi,
I've got query like this:
select count(ID) from TABLE where (TABLE.A + TABLE.B + TABLE.C + TABLE.D)
0
A,B,C,D are decimal values.
There are over 1 records where A is greater than 0,
about 1000 where B is greater than 0,
about 500 where C is greater than 0,
and about 300 where D is
27 matches
Mail list logo
