Yes, that was what I planned to do but I have not studied the Howto's very
carefully. I just did not know how access would write in its ouput file
and how MySQL would take them. It is rather obvious for Strings or Int
values but not for booleans. But anyways, I think I just need to try it
out.
H
On Thu, 20 Apr 2000, Michael Yuan wrote:
>
> Thanks for the replies. Yes, I know there are ways to work around. I am
> using strings "true" and "false" currently (I do not care too much about
> memory :). But my major concern was that when I transfer a database with
> boolean type support to MyS
Thanks for the replies. Yes, I know there are ways to work around. I am
using strings "true" and "false" currently (I do not care too much about
memory :). But my major concern was that when I transfer a database with
boolean type support to MySQL (like, a database entered by a secretry in
ms acc
MySQL does not have a boolean type. There really isnt a need for it
though, since an tinyint will do in a pinch, and doesnt take up any
more memory.
brax.
On Thu, 20 Apr 2000, Michael Yuan wrote:
>
> It is true that MySQL does not have boolean data type? I did not see that
> on the mannual a
If it's not in the manual, they don't have it. You can probably use ENUM
or SET instead.
On Thu, 20 Apr 2000, Michael Yuan wrote:
>
> It is true that MySQL does not have boolean data type? I did not see that
> on the mannual and the database refuse to take boolean as column data type
> ...
