Access to mysql using the mysql migration tool: 

What to do with booleans? They all went to -1 and queries now turn up nothing. 
Do I need to set them all to 1 and that's it? I read something about 
signed/unsigned but have no idea what that means.

Is there a list of gotchas anywhere that people know of? I'm wondering:

1) what columns or datatypes I'm going to have to check and repair like the 
booleans (why didn't the migration fix that???)

2)  what sort of things I'm going to have recode in the queries (already saw 
one timestamp error)

3) anything else I'm going to have to setup or do with the db? I have no real 
clue about databases, what a stored procedure is, indexing, anything. I'm 
converting an old web app to mysql on my own. I'd like to avoid anything that 
will slow it down unnecessarily :-)

I'm surprised the mysql gui doesn't have a dropdown of datatypes to select 
from. Is there a good list anyone knows of?

Thanks.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Upgrade to Adobe ColdFusion MX7 
Experience Flex 2 & MX7 integration & create powerful cross-platform RIAs 
http:http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU

Archive: http://www.houseoffusion.com/groups/SQL/message.cfm/messageid:2709
Subscription: http://www.houseoffusion.com/groups/SQL/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.6

Reply via email to