AllowZeroLength vs NOT NULL
I'm converting an Access 97 app to MySQL with web pages and such via an AMP stack and I am a little confused over a couple of differences. I'm hoping I can get clarification here.
I've executed the Database Documenter in Access and have a rather large text file I'm using as a template to guide my schema development in MySQL (hope that's the right terminology). But, I'm kinda stuck on the issue of Access' AllowZeroLength and MySQL's NOT NULL attributes.
I'm under the impression that an AllowZeroLength setting of false would require that something be in that field. This seems to match up nicely with the NOT NULL attribute of a column in MySQL. First of all, am I correct on this?
Secondly, in Access I also see an attribute of 'Required', which is also a true/false condition, that in my mind seems redundant for a field. If an Access field has AllowZeroLength set to false and Required set to true, are they doing the same thing? It seems at first that I can accomplish the same thing in MySQL by merely setting the NOT NULL attribute on a field.
How's my thinking on this so far?
Subject
Views
Written By
Posted
AllowZeroLength vs NOT NULL
2288
July 25, 2016 04:47PM
1104
July 26, 2016 07:36AM
1333
July 26, 2016 11:08PM
1335
July 27, 2016 02:31PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.