Merge lp:~vkolesnikov/pbxt/pbxt-type-enum into lp:pbxt

[Vladimir Kolesnikov]

[Vladimir Kolesnikov (vkolesnikov)]

Tests fixed. However once I was able to see the old style behavior with this test - an error on table creation. I was not able to reproduce it anymore. I propose this for merging because I think this is the correct behavior. IMO it would be illogical to create "exhausting" enum that involves all characters from latin1 just to check that it really fails because of back slashes mode.

[Paul McCullagh (paul-mccullagh)]

Hi Vlad,

Was there a reason for removing "drop database pbxt"?

This change was required by MariaDB which tests that the state of the
server is the same as before and after each test.

On May 29, 2009, at 10:40 AM, Vladimir Kolesnikov wrote:

> --disable_query_log
> -drop database pbxt;
> ---enable_query_log
> +#--disable_query_log
> +#drop database pbxt;
> +#--enable_query_log
> --echo End of 5.1 tests

--
Paul McCullagh
PrimeBase Technologies
www.primebase.org
www.blobstreaming.org
pbxt.blogspot.com

[Vladimir Kolesnikov (vkolesnikov)]

yes, the problem was I got an error like: cannot drop dtabase pbxt,
cannot delete table "statistics,locations"

Paul McCullagh wrote:
> Hi Vlad,
>
> Was there a reason for removing "drop database pbxt"?
>
> This change was required by MariaDB which tests that the state of the
> server is the same as before and after each test.
>
> On May 29, 2009, at 10:40 AM, Vladimir Kolesnikov wrote:
>
>
>> --disable_query_log
>> -drop database pbxt;
>> ---enable_query_log
>> +#--disable_query_log
>> +#drop database pbxt;
>> +#--enable_query_log
>> --echo End of 5.1 tests
>>
>
>
>
> --
> Paul McCullagh
> PrimeBase Technologies
> www.primebase.org
> www.blobstreaming.org
> pbxt.blogspot.com
>
>
>
>

--
--
Best Regards,
Vladimir

[Paul McCullagh (paul-mccullagh)]

I have seen this kind of thing before. I think it is a bug, and should
be investigated.

I all PBXT tables are dropped first, the it should always be possible
to do:

drop database pbxt;

On May 29, 2009, at 12:36 PM, Vladimir Kolesnikov wrote:

> yes, the problem was I got an error like: cannot drop dtabase pbxt,
> cannot delete table "statistics,locations"
>
> Paul McCullagh wrote:
>> Hi Vlad,
>>
>> Was there a reason for removing "drop database pbxt"?
>>
>> This change was required by MariaDB which tests that the state of the
>> server is the same as before and after each test.
>>
>> On May 29, 2009, at 10:40 AM, Vladimir Kolesnikov wrote:
>>
>>
>>> --disable_query_log
>>> -drop database pbxt;
>>> ---enable_query_log
>>> +#--disable_query_log
>>> +#drop database pbxt;
>>> +#--enable_query_log
>>> --echo End of 5.1 tests
>>>
>>
>>
>>
>> --
>> Paul McCullagh
>> PrimeBase Technologies
>> www.primebase.org
>> www.blobstreaming.org
>> pbxt.blogspot.com
>>
>>
>>
>>
>
>
> --
> --
> Best Regards,
> Vladimir
>
> https://code.launchpad.net/~vkolesnikov/pbxt/pbxt-type-enum/+merge/
> 6878
> Your team PBXT Core is subscribed to branch lp:pbxt.

--
Paul McCullagh
PrimeBase Technologies
www.primebase.org
www.blobstreaming.org
pbxt.blogspot.com

[Vladimir Kolesnikov (vkolesnikov)]

ok, I will check. My first guess was that this is a MySQL problem
because pbxt is not a normal database (?)...

Paul McCullagh wrote:
> I have seen this kind of thing before. I think it is a bug, and should
> be investigated.
>
> I all PBXT tables are dropped first, the it should always be possible
> to do:
>
> drop database pbxt;
>
> On May 29, 2009, at 12:36 PM, Vladimir Kolesnikov wrote:
>
>
>> yes, the problem was I got an error like: cannot drop dtabase pbxt,
>> cannot delete table "statistics,locations"
>>
>> Paul McCullagh wrote:
>>
>>> Hi Vlad,
>>>
>>> Was there a reason for removing "drop database pbxt"?
>>>
>>> This change was required by MariaDB which tests that the state of the
>>> server is the same as before and after each test.
>>>
>>> On May 29, 2009, at 10:40 AM, Vladimir Kolesnikov wrote:
>>>
>>>
>>>
>>>> --disable_query_log
>>>> -drop database pbxt;
>>>> ---enable_query_log
>>>> +#--disable_query_log
>>>> +#drop database pbxt;
>>>> +#--enable_query_log
>>>> --echo End of 5.1 tests
>>>>
>>>>
>>>
>>> --
>>> Paul McCullagh
>>> PrimeBase Technologies
>>> www.primebase.org
>>> www.blobstreaming.org
>>> pbxt.blogspot.com
>>>
>>>
>>>
>>>
>>>
>> --
>> --
>> Best Regards,
>> Vladimir
>>
>> https://code.launchpad.net/~vkolesnikov/pbxt/pbxt-type-enum/+merge/
>> 6878
>> Your team PBXT Core is subscribed to branch lp:pbxt.
>>
>
>
>
> --
> Paul McCullagh
> PrimeBase Technologies
> www.primebase.org
> www.blobstreaming.org
> pbxt.blogspot.com
>
>
>
>

--
--
Best Regards,
Vladimir

[Paul McCullagh (paul-mccullagh)]

On May 29, 2009, at 1:03 PM, Vladimir Kolesnikov wrote:

> ok, I will check.

Thanks.

> My first guess was that this is a MySQL problem
> because pbxt is not a normal database (?)...

Yes, it is not a normal database however, I still expect it to work
because all tests end with "drop database pbxt".

Since the other tests do not indicate a problem, there must be
something different happening in this case.

So I would be interested to find out what.

A bit of background:

MySQL drops the database by dropping all the tables in the database,
and then removing the database folder.

PBXT allows the "statistics" and "location" tables to be dropped if
there are no existing PBXT tables.

Note statistics and location are normal tables from the MySQL point of
view. They both have .frm files.

When the last system table is dropped, PBXT also removes the "system"
and "data" folders in the pbxt directory.

In this way the pbxt directory should then be empty and MySQL should
be able to remove it.

> Paul McCullagh wrote:
>> I have seen this kind of thing before. I think it is a bug, and
>> should
>> be investigated.
>>
>> I all PBXT tables are dropped first, the it should always be possible
>> to do:
>>
>> drop database pbxt;
>>
>> On May 29, 2009, at 12:36 PM, Vladimir Kolesnikov wrote:
>>
>>
>>> yes, the problem was I got an error like: cannot drop dtabase pbxt,
>>> cannot delete table "statistics,locations"
>>>
>>> Paul McCullagh wrote:
>>>
>>>> Hi Vlad,
>>>>
>>>> Was there a reason for removing "drop database pbxt"?
>>>>
>>>> This change was required by MariaDB which tests that the state of
>>>> the
>>>> server is the same as before and after each test.
>>>>
>>>> On May 29, 2009, at 10:40 AM, Vladimir Kolesnikov wrote:
>>>>
>>>>
>>>>
>>>>> --disable_query_log
>>>>> -drop database pbxt;
>>>>> ---enable_query_log
>>>>> +#--disable_query_log
>>>>> +#drop database pbxt;
>>>>> +#--enable_query_log
>>>>> --echo End of 5.1 tests
>>>>>
>>>>>
>>>>
>>>> --
>>>> Paul McCullagh
>>>> PrimeBase Technologies
>>>> www.primebase.org
>>>> www.blobstreaming.org
>>>> pbxt.blogspot.com
>>>>
>>>>
>>>>
>>>>
>>>>
>>> --
>>> --
>>> Best Regards,
>>> Vladimir
>>>
>>> https://code.launchpad.net/~vkolesnikov/pbxt/pbxt-type-enum/+merge/
>>> 6878
>>> Your team PBXT Core is subscribed to branch lp:pbxt.
>>>
>>
>>
>>
>> --
>> Paul McCullagh
>> PrimeBase Technologies
>> www.primebase.org
>> www.blobstreaming.org
>> pbxt.blogspot.com
>>
>>
>>
>>
>
>
> --
> --
> Best Regards,
> Vladimir
>
> https://code.launchpad.net/~vkolesnikov/pbxt/pbxt-type-enum/+merge/
> 6878
> Your team PBXT Core is subscribed to branch lp:pbxt.

--
Paul McCullagh
PrimeBase Technologies
www.primebase.org
www.blobstreaming.org
pbxt.blogspot.com

[Vladimir Kolesnikov (vkolesnikov)]

ah ok, then I think I knwo what the problem: PBXT doesn't allow it to be
removed, as the script doesn't drop the last table, as beore the fix it
was not supposed to be created...

Paul McCullagh wrote:
> On May 29, 2009, at 1:03 PM, Vladimir Kolesnikov wrote:
>
>
>> ok, I will check.
>>
>
> Thanks.
>
>
>> My first guess was that this is a MySQL problem
>> because pbxt is not a normal database (?)...
>>
>
> Yes, it is not a normal database however, I still expect it to work
> because all tests end with "drop database pbxt".
>
> Since the other tests do not indicate a problem, there must be
> something different happening in this case.
>
> So I would be interested to find out what.
>
> A bit of background:
>
> MySQL drops the database by dropping all the tables in the database,
> and then removing the database folder.
>
> PBXT allows the "statistics" and "location" tables to be dropped if
> there are no existing PBXT tables.
>
> Note statistics and location are normal tables from the MySQL point of
> view. They both have .frm files.
>
> When the last system table is dropped, PBXT also removes the "system"
> and "data" folders in the pbxt directory.
>
> In this way the pbxt directory should then be empty and MySQL should
> be able to remove it.
>
>
>> Paul McCullagh wrote:
>>
>>> I have seen this kind of thing before. I think it is a bug, and
>>> should
>>> be investigated.
>>>
>>> I all PBXT tables are dropped first, the it should always be possible
>>> to do:
>>>
>>> drop database pbxt;
>>>
>>> On May 29, 2009, at 12:36 PM, Vladimir Kolesnikov wrote:
>>>
>>>
>>>
>>>> yes, the problem was I got an error like: cannot drop dtabase pbxt,
>>>> cannot delete table "statistics,locations"
>>>>
>>>> Paul McCullagh wrote:
>>>>
>>>>
>>>>> Hi Vlad,
>>>>>
>>>>> Was there a reason for removing "drop database pbxt"?
>>>>>
>>>>> This change was required by MariaDB which tests that the state of
>>>>> the
>>>>> server is the same as before and after each test.
>>>>>
>>>>> On May 29, 2009, at 10:40 AM, Vladimir Kolesnikov wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> --disable_query_log
>>>>>> -drop database pbxt;
>>>>>> ---enable_query_log
>>>>>> +#--disable_query_log
>>>>>> +#drop database pbxt;
>>>>>> +#--enable_query_log
>>>>>> --echo End of 5.1 tests
>>>>>>
>>>>>>
>>>>>>
>>>>> --
>>>>> Paul McCullagh
>>>>> PrimeBase Technologies
>>>>> www.primebase.org
>>>>> www.blobstreaming.org
>>>>> pbxt.blogspot.com
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>> --
>>>> --
>>>> Best Regards,
>>>> Vladimir
>>>>
>>>> https://code.launchpad.net/~vkolesnikov/pbxt/pbxt-type-enum/+merge/
>>>> 6878
>>>> Your team PBXT Core is subscribed to branch lp:pbxt.
>>>>
>>>>
>>>
>>> --
>>> Paul McCullagh
>>> PrimeBase Technologies
>>> www.primebase.org
>>> www.blobstreaming.org
>>> pbxt.blogspot.com
>>>
>>>
>>>
>>>
>>>
>> --
>> --
>> Best Regards,
>> Vladimir
>>
>> https://code.launchpad.net/~vkolesnikov/pbxt/pbxt-type-enum/+merge/
>> 6878
>> Your team PBXT Core is subscribed to branch lp:pbxt.
>>
>
>
>
> --
> Paul McCullagh
> PrimeBase Technologies
> www.primebase.org
> www.blobs...

[Paul McCullagh (paul-mccullagh)]

Ah - terrible error message!

On May 29, 2009, at 1:24 PM, Vladimir Kolesnikov wrote:

> ah ok, then I think I knwo what the problem: PBXT doesn't allow it
> to be
> removed, as the script doesn't drop the last table, as beore the fix
> it
> was not supposed to be created...
>
> Paul McCullagh wrote:
>> On May 29, 2009, at 1:03 PM, Vladimir Kolesnikov wrote:
>>
>>
>>> ok, I will check.
>>>
>>
>> Thanks.
>>
>>
>>> My first guess was that this is a MySQL problem
>>> because pbxt is not a normal database (?)...
>>>
>>
>> Yes, it is not a normal database however, I still expect it to work
>> because all tests end with "drop database pbxt".
>>
>> Since the other tests do not indicate a problem, there must be
>> something different happening in this case.
>>
>> So I would be interested to find out what.
>>
>> A bit of background:
>>
>> MySQL drops the database by dropping all the tables in the database,
>> and then removing the database folder.
>>
>> PBXT allows the "statistics" and "location" tables to be dropped if
>> there are no existing PBXT tables.
>>
>> Note statistics and location are normal tables from the MySQL point
>> of
>> view. They both have .frm files.
>>
>> When the last system table is dropped, PBXT also removes the
>> "system"
>> and "data" folders in the pbxt directory.
>>
>> In this way the pbxt directory should then be empty and MySQL should
>> be able to remove it.
>>
>>
>>> Paul McCullagh wrote:
>>>
>>>> I have seen this kind of thing before. I think it is a bug, and
>>>> should
>>>> be investigated.
>>>>
>>>> I all PBXT tables are dropped first, the it should always be
>>>> possible
>>>> to do:
>>>>
>>>> drop database pbxt;
>>>>
>>>> On May 29, 2009, at 12:36 PM, Vladimir Kolesnikov wrote:
>>>>
>>>>
>>>>
>>>>> yes, the problem was I got an error like: cannot drop dtabase
>>>>> pbxt,
>>>>> cannot delete table "statistics,locations"
>>>>>
>>>>> Paul McCullagh wrote:
>>>>>
>>>>>
>>>>>> Hi Vlad,
>>>>>>
>>>>>> Was there a reason for removing "drop database pbxt"?
>>>>>>
>>>>>> This change was required by MariaDB which tests that the state of
>>>>>> the
>>>>>> server is the same as before and after each test.
>>>>>>
>>>>>> On May 29, 2009, at 10:40 AM, Vladimir Kolesnikov wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> --disable_query_log
>>>>>>> -drop database pbxt;
>>>>>>> ---enable_query_log
>>>>>>> +#--disable_query_log
>>>>>>> +#drop database pbxt;
>>>>>>> +#--enable_query_log
>>>>>>> --echo End of 5.1 tests
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> --
>>>>>> Paul McCullagh
>>>>>> PrimeBase Technologies
>>>>>> www.primebase.org
>>>>>> www.blobstreaming.org
>>>>>> pbxt.blogspot.com
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>> --
>>>>> --
>>>>> Best Regards,
>>>>> Vladimir
>>>>>
>>>>> https://code.launchpad.net/~vkolesnikov/pbxt/pbxt-type-enum/
>>>>> +merge/
>>>>> 6878
>>>>> Your team PBXT Core is subscribed to branch lp:pbxt.
>>>>>
>>>>>
>>>>
>>>> --
>>>> Paul McCullagh
>>>> PrimeBase Technologies
>>>> www.primebase.org
>>>> www.blobstreaming.org
>>>> pbxt.blogspot.com
>>>>
>>>>
>>>>
>>>>
>>>>
>>> --
>>> --
>>> Best Regards,
>>> Vladimir
>>>
>>> https://code.launchpad.net/~vkolesnikov/pbxt/pbxt-type-enum/+merge/
>>> 6878...

[lp:~vkolesnikov/pbxt/pbxt-type-enum]

654. By Vladimir Kolesnikov on 2009-05-29

updated script to allow dropping pbxt database

=== modified file 'test/mysql-test/r/type_enum.result'
--- test/mysql-test/r/type_enum.result	2008-09-17 07:41:28 +0000
+++ test/mysql-test/r/type_enum.result	2009-05-29 08:23:28 +0000
@@ -1776,8 +1776,13 @@
   `russian_deviant` enum('E','F','EÿF','F,E') NOT NULL DEFAULT 'E'
 ) ENGINE=PBXT DEFAULT CHARSET=latin1
 drop table t1;
+select @@SESSION.sql_mode;
+@@SESSION.sql_mode
+
+select @@GLOBAL.sql_mode;
+@@GLOBAL.sql_mode
+
 create table t1(exhausting_charset enum('ABCDEFGHIJKLMNOPQRSTUVWXYZ','
	
 


 


 !"','#$%&\'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^_`abcdefghijklmnopqrstuvwxyz{|}~','xx\','yy\€','zz�‚ƒ„…†‡ˆ‰Š‹Œ�Ž��‘’“”•–—˜™š›œ�žŸ ¡¢£¤¥¦§¨©ª«¬­®¯°±²³´µ¶·¸¹º»¼½¾¿ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿ'));
-ERROR HY000: Can't create table 'test.t1' (errno: -1)
 End of 5.1 tests

=== modified file 'test/mysql-test/t/type_enum.test'
--- test/mysql-test/t/type_enum.test	2009-04-02 20:28:52 +0000
+++ test/mysql-test/t/type_enum.test	2009-05-29 08:23:28 +0000
@@ -153,13 +153,18 @@
 show create table t1;
 drop table t1;
 
-# ER_WRONG_FIELD_TERMINATORS
---error 1005
+# the following create statement sometimes fails like it would if NO_BACKSLASH_ESCAPES sql mode was on,
+# we check sql mode here
+select @@SESSION.sql_mode;
+select @@GLOBAL.sql_mode;
+
+## ER_WRONG_FIELD_TERMINATORS
+#--error 1005
 create table t1(exhausting_charset enum('ABCDEFGHIJKLMNOPQRSTUVWXYZ','
	
 


 


 !"','#$%&\'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^_`abcdefghijklmnopqrstuvwxyz{|}~','xx\','yy\€','zz�‚ƒ„…†‡ˆ‰Š‹Œ�Ž��‘’“”•–—˜™š›œ�žŸ ¡¢£¤¥¦§¨©ª«¬­®¯°±²³´µ¶·¸¹º»¼½¾¿ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿ'));
 
---disable_query_log
-drop database pbxt;
---enable_query_log
+#--disable_query_log
+#drop database pbxt;
+#--enable_query_log
 --echo End of 5.1 tests