Re: create table....select * from table anomaly..

2004-10-19 Thread Egor Egorov 
It's rather a different behaviour. We suggest to upgrade to 4.0.21 in this
case. 





-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.net http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Egor Egorov
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.net
   <___/   www.mysql.com




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

create table....select * from table anomaly..

2004-10-15 Thread Karam Chand 
Hello,

I have three databases 3.23.54 (production) & 4.0.18
and 4.1.3 as test servers.

I execute the following sqls:

>>>
create database testdb;

use testdb;

CREATE TABLE `test` ( 
  
`example_col` varchar(100) default NULL   

  ) TYPE=MyISAM;

create table `test_copy` type=MyISAM select
`example_col` from `test` where 1 = 0;>>

In 3.23.54, the example_col of test_copy gets
converted to char(100) whereas it remains same in i.e.
varchar (which I want) in 4.0.18 and 4.1.1.

Is it a known issue or it was a bug with 3.23.54 that
has been solved?

Regards,
Karam




___
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]