Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Oracle does not support a bit datatype or any other type for true/false scenarios. Does one use the char(1) field instead by using a specific letter to denote yes / true regardless of culture specific issues?
Instead of char should it be Number(1,0) for this instead – 0 being considered false / no, anything else being interpreted as true / yes?
Is this viable?
Why does Oracle not support a simple boolean type?
I prefer char(1) over number(1), since with some reasonable choice of characters, it is obvious which character has which boolean meaning.
Of course you should fight all the different varations, choose one and ensure it’s use by putting check constraints on the columns.
Although it probably is to late in your case, generating the schema from another tool often takes care at least of the consistency issue. I personally prefer hibernate for this purpose, but that is very situation specific.
And of course that is a glaring obmission. To make it worse, PL/SQL has a boolean, but you can’t use it in SQL statements.