Use VARCHAR2 rather than VARCHAR on Oracle

[Former user]

Oracle VARCHAR and VARCHAR2 are operationally the same in Oracle, but Oracle recommends the use of VARCHAR2, choosing to preserve VARHCAR for future use. When VARCHAR is used in the schema definition Oracle actually generates a VARCHAR2.

In order to be consistent with Oracle's recommendation and for what is in the database to match the schema definition, I suggest that VARCHAR2 be used in place of VARCHAR in the Oracle engine.

[Mike Bayer]

we'll use VARCHAR2 for String, as well as a new type VARCHAR2. If someone explicitly puts VARCHAR i still think we should stick to the "uppercase=WYSIWYG" policy - Oracle is never going to change VARCHAR IMHO - but if they did, then VARCHAR should be generating the string VARCHAR in any case since it actually means something.

3f347edd14cf9ab1b01c7570a65228d964d2b4a6

[Mike Bayer]

Removing milestone: 0.7.3 (automated comment)