2014-11-06 21:49 GMT+01:00, Roberta Jaskólski :
> Ugh--I missed the discussion shift from the DATEs to the VARCHAR labels ...
> and now I wholeheartedly agree with you.
>
> As for the DATEs, I yet suspect that for performance maybe TIMESTAMP is
> slightly better than DATE.
Well what I'm interest
2014-10-31 5:29 GMT+01:00, Jan Steinman :
> What about using ENUMs? They have nearly the performance of INTEGERs, but
> you don't have to maintain a string mapping in your programming logic.
So you guys (Jan and "hsv") suggest, that switching from DATE to "more
numeric" data type may not be neces
I'm going to establish a large database (ISAM) of simple structure,
say the table with only 3 columns:
- VARCHAR(80)
- VARCHAR(40)
- DATE
The number of rows can be quite large, about hundred million or so.
The first column, containing actual information, will contain unique
values, unlike the two
id give it a try and all is fine with the index file. So this is
not the problem. Thanks!
--
Zbigniew Szalbot
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
ot;)
Yes, it was referring to the correct location so seems like a bug of some sort.
> http://lists.mysql.com/mysql/206576
I found a mention here about a cronjob which I implemented and I am
happy with it. Thanks!
--
Zbigniew Szalbot
--
MySQL General Mailing List
For list archives: http:/
-server-5.0.67 on FreeBSD 7.0-Release machine.
Many thanks!
--
Zbigniew Szalbot
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Hello !
I have a following problem while scripting MySQL with PHP4:
Imagine the user may add a record to a table. How can I know precisely what was the
number (auto increment primary key) given by MySQL to this new inserted row ??? You
may presume there are many simultaneus users adding rows,
Hello !
This is a syntax taken from MS Access:
SELECT messages.message_id, messages_1.message_id
FROM messages AS messages_1 INNER JOIN (messages INNER JOIN connections ON
messages.message_id = connections.parent) ON messages_1.message_id = connections.child
ORDER BY messages.message_id, messag
