RE: About Data types

Depending on how many records you anticipate in your table, you might want
to use "BIGINT" for the field type for your primary key.  Also, "BIT" is
defined as a single bit field.  I think I saw that it's implemented as a
byte so you wouldn't save any storage in this implementation of MySQL.
Also, by leaving it as TINYINT, you'll eliminate a manual edit of the
resulting imported table.

Regards.



Lawson Cronlund
[email protected]
+1(480)308-0641 (Voice)
+1(602)996-0376 (Fax)
 

-----Original Message-----
From: [email protected] [mailto:[email protected]] 
Sent: Sunday, March 19, 2006 4:07 PM
To: [email protected]; [email protected]
Cc: [email protected]
Subject: RE: About Data types


There is no specific autonumber field type in MySQL so 'Int' is what you
want with the autoinc property set. Also MySQL has no Boolean type so
tinyint is probably the best alternative.

The problem with #deleted is usually solved by including a timestamp
column in each table, although I have never needed to do that. Make sure
all tables have a primary key defined.

John B.

-----Original Message-----
From: shreeseva [mailto:[email protected]] 
Sent: Monday, 20 March 2006 6:16 AM
To: [email protected]
Cc: [email protected]
Subject: About Data types

Dear friends,
I am using MySQL 5.0.17 on Win XP Prof. I have created a prototype
database design in Ms Access 2003 and using MySQL Migration tool
uploaded this to MySQL server. I have encounterred few problems with it.

1) Migration toolkit successfully transfered all tabels and indexes but
all Autonumber fields are transfered as 'int'. Also all boolean
fields(In Access 'Yes/No' ) are transfered as 'tinyint'. Is there a bug
the toolkit?
2) When I go for data entry through Access form It displays as
'#deleted' in all fields. Why?
I am entering data from Master form and when control goes into the
Subform linked with the master form it makes all entered fileds as
'#deleted'. The master form is related with documents table having one
field as AutoIncrement and subform is based on Transactions for that
document. This Transactions table also contains one Autoincrement filed.
Both such fileds are PK's also.
Now when I changed the AutoIncrement to 'No' for Documents table it goes
correctly and not displayed '#deleted'. But when I entered data into
Transactions table having AutoIncrement still to 'Yes' then it displayed
as '#deleted'. Why?
Is this a bug or my mistake or ODBC driver problem or Access problem?

Please help
Thanks and regards.

CPK

-- 
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe:    http://lists.mysql.com/[email protected]


-- 
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe:    http://lists.mysql.com/[email protected]