mySQL and defaults

Bob Sneidar bobs at
Fri Mar 18 12:02:15 EDT 2011

Right sorry I discovered this last night too. I think the problem was the Sequel Quotes. For some reason I was replacing not only double quotes with ` but single ones too. Trouble is, you cannot wrap default values in `. Also, the reference manual says that text types did not support DEFAULT. I assumed (much to my chagrin) that varchar was a text type. 

I found that a quick way to tell if my sequel is good is to step through the code until I have my statement, then copy the sequel fom the variable browser into the query editor in MySQLWorkbench. It will put a red X at the first line that has bad syntax. Very handy for troubleshooting Sequel, especially since when I build my Sequel, I try to isolate each statement on it's own line. 


On Mar 17, 2011, at 6:57 PM, Warren Samples wrote:

> On Thursday, March 17, 2011 02:00:41 PM Bob Sneidar wrote:
>> Oh thanks Warren! That will work famously! Unfortunately I just finished
>> the code that strips all the DEFAULT parameters from all text column
>> definitions LOL! I guess it's back to work undoing my last undo. Still,
>> nice to know it can be done.
>> Bob
> Hi Bob,
> I just tried this myself and find that the NOT NULL doesn't seem to have been 
> the key since this works, too:
> DEFAULT 'Unknown');
> Query OK, 0 rows affected (0.04 sec)
> So, perhaps there was some other error in your query? Punctuation and spelling 
> are the usual suspects ;)
> Best,
> Warren
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

More information about the Use-livecode mailing list