- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
- 09
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
CREATE TABLE `cache_lead_emails` (
`id` INT(10) NOT NULL AUTO_INCREMENT,
`created_on_date` DATETIME NULL DEFAULT NULL,
`some_id_1` BIGINT(20) NULL DEFAULT NULL,
`some_id_2` BIGINT(20) NULL DEFAULT NULL,
`some_id_3` BIGINT(20) NULL DEFAULT NULL,
`some_id_4` BIGINT(20) NULL DEFAULT NULL,
`index_letter` VARCHAR(1) NULL DEFAULT NULL,
`writable` ENUM('Yes','No') NULL DEFAULT NULL,
`emails` TEXT NULL,
PRIMARY KEY (`id`)
)
COLLATE='utf8_general_ci'
ENGINE=InnoDB
"4" "2013-03-12 17:56:38" "1" "3" "3" "3" "G" "Yes" "4:g****@gmail.com,26:g****@hotmail.com,29:g*****@hotmail.com,116:g****@gmail.com"
"5" "2013-03-12 17:56:38" "1" "3" "3" "3" "I" "Yes" "5:i******@gmail.com,44:i*****@gmail.com"
Sorry for the English.
This is a cache table holding emails separated by letter. For example I`ve shown all e-mails starting with G ( its only one row for all of them). I still don`t know where the digits separating the e-mails come from.
The field "writable" is set to "No" immediately before update and hen updated to "Yes" after update so .. it basically is creative LOCK mechanism :)
brilliant!
Google translate:
Извините за английский язык.
Это кэш-стол с электронной почты, разделенных буквой. Например, я `ве показаны все сообщения электронной почты, начинающиеся с G (ее только одна строка для каждого из них). Я до сих пор не знаю, где цифры отделения электронной почты родом.
В поле "записи" установлен в положение "No" непосредственно перед обновления и курица обновленный "Yes" после обновления так .. это в принципе творческого механизма LOCK :)
блестящий
DBdev 13.03.2013 16:30 # +2
> я `ве
> и курица обновленный "Yes"
> творческого механизма
Please, DO NOT use google translate!
gotha 13.03.2013 18:08 # 0
Despite the fact I am slav, I don`t know Russian at all, I understand some words, but I can`t build a sentance so I thought that GT can be at least a little bit of help.
I cannot edit it,so please, admins, if you think it is necessary, delete my post.
Regards.
eth0 13.03.2013 18:37 # +3
Да и английский не очень.
torbasow 14.03.2013 08:44 # +1
DBdev 13.03.2013 19:54 # +4
So you do not need any kind of translators.
nonamez 13.03.2013 16:46 # +3
nonamez 13.03.2013 16:47 # −1
krypt 14.03.2013 20:36 # 0
eth0 13.03.2013 17:51 # +3
I will not buy this record, it is scratched. My hovercraft is full of eels. Do you want... do you want... to come back to my place, bouncy bouncy? If I said you had a beautiful body, would you hold it against me... I am no longer infected.
Hope it will help, with best regards.
DBdev 13.03.2013 17:56 # 0
Check respective cache_lead_emails.id's
> The field "writable" is set to "No" immediately before update and hen updated to "Yes" after update so .. it basically is creative LOCK mechanism :)
Probably, some "INSTEAD OF UPDATE" trigger exists on a table which is checking "writable" column state? In this case it doesn't look useless...
gotha 13.03.2013 18:04 # 0
No, no such trigger.
mac-t 14.03.2013 00:02 # 0
guest 16.03.2013 17:08 # −3
ncuxonam 25.08.2021 08:03 # 0