Something like Decimal(19,4) usually works pretty well in most cases. You can adjust the scale and precision to fit the needs of the numbers you need to store. Even in SQL Server, I tend not to use “money” as it’s non-standard.
Not only is the boolean datatype missing in Oracle’s SQL (not PL/SQL), but they also have no clear recommendation about what to use instead. See this thread on asktom. From recommending CHAR(1) ‘Y”https://stackoverflow.com/”N’ they switch to NUMBER(1) 0/1 when someone points out that ‘Y”https://stackoverflow.com/”N’ depends on the English language, while e.g. German programmers might use … Read more
As for now, they are synonyms. VARCHAR is reserved by Oracle to support distinction between NULL and empty string in future, as ANSI standard prescribes. VARCHAR2 does not distinguish between a NULL and empty string, and never will. If you rely on empty string and NULL being the same thing, you should use VARCHAR2.
TEXT is used for large pieces of string data. If the length of the field exceeed a certain threshold, the text is stored out of row. VARCHAR is always stored in row and has a limit of 8000 characters. If you try to create a VARCHAR(x), where x > 8000, you get an error: Server: … Read more
Since money needs an exact representation don’t use data types that are only approximate like float. You can use a fixed-point numeric data type for that like decimal(15,2) 15 is the precision (total length of value including decimal places) 2 is the number of digits after decimal point See MySQL Numeric Types: These types are … Read more
For MySQL 5.0.3 and higher, you can use BIT. The manual says: As of MySQL 5.0.3, the BIT data type is used to store bit-field values. A type of BIT(M) enables storage of M-bit values. M can range from 1 to 64. Otherwise, according to the MySQL manual you can use BOOL or BOOLEAN, which … Read more
Should I use the datetime or timestamp data type in MySQL?