SQL and other databases

[Peter Haworth]

Not seeing it on those types either:

`testdefault` char(10) DEFAULT 'XYZ',
`testdefault2` varchar(10) DEFAULT 'ABC',

Worked fine for me (through Sequel Pro).  I wonder if this is a difference between versions of MySQL.  I'm using the Community version which is the free one.

You're right on the TEXT types not allowing defaults although why that should be is a mystery.  

Pete Haworth

On Mar 22, 2011, at 11:54 AM, Bob Sneidar wrote:

> Yes but those are numeric data types. The restriction was on the char types char() and varchar() (if I am not mistaken). TEXT types do not allow defaults at all according to the manual. 
> 
> Bob
> 
> 
> On Mar 22, 2011, at 10:29 AM, Peter Haworth wrote:
> 
>> Hi Bob,
>> I'm slowly putting together a list of differences between SQLite and MySQL.  I'm concentrating on things that SQLite allows and MySQL does not.  I haven't looked at extra functionality provided by MySQL over and above what SQLite provides since right now I just want to get to the point that my SQLite schema definitions and data manipulation statements work in MySQL
>> 
>> Before getting to the list, a couple of observations on the issues you've come across.  
>> 
>> I'm not seeing the requirement to have NOT NULL in conjunction with DEFAULT.  Here's a snippet which was accepted just fine by mySQL:
>> 
>> `BandTrakSalesID` int(11) DEFAULT '0',
>> `Selected` tinyint(1) DEFAULT '1',
> 
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>