Rick Hillegas wrote:
Hi Satheesh,
TINYINT, as you note, is not an ANSI datatype. It is, however, a JDBC
datatype and is supported by MySQL and SQL Server. Adding it would
grow our JDBC support and help close the feature gap with some
significant databases. I think those are compelling arguments.
Fortunately, TINYINT is already supported by Derby--it was only
lightly disabled when the non-DB2 datatypes were hidden. Re-enabling
it should be easy.
Sybase also support this
ROWID is another JDBC type. to be added as part of the JDBC 4.0
effort. It underlies the java.sql.RowId interface. Oracle calls these
columns ROWIDs and Postgres calls them OIDs. This type needs some
specifying.
DB2 supports this as do other databases. MySQL has a special column
name __rowid which can be used if there is a Primary Key or Unique which
is an integer
Enhancement requests 499 and 533 track the re-enabling of BOOLEAN and
national character datatypes.
TINYINT and ROWID deserve their own enhancement requests. I agree that
an overall spec would be useful to make sure that we consistently
handle the cross-release and client-server compatibility issues. I'll
get around to this soon hopefully.
Cheers,
-Rick
Satheesh Bandaram wrote:
Hi Rick,
Pretty interesting... I hope you will find time to make a detailed
proposal available for community review.
SQL standard, as you probably know, doesn't support TINYINT or ROWID.
TINYINT especially is not defined by DB2, Oracle... Also, how are you
planning on defining ROWID and what is its main purpose?
Hope you will share your thoughts early...
Satheesh
Rick Hillegas wrote:
Hi Satheesh,
Thanks for tracking these proposals. Here are the datatypes I want to
add, re-enable, or extend in the 10.2 timeframe:
BOOLEAN
TINYINT
NCHAR
NVARCHAR
LONGNVARCHAR
NCLOB
ROWID
SQLXML
Cheers,
-Rick
Satheesh Bandaram wrote:
I noticed several other new feature work being proposed and actively
being worked, possibly in time for next 10.2 release. Here is the
updated list I have so far. Let me know if I missed anything.
1. JDBC 4.0 Stub implementation
2. Unary Plus/Minus.
3. Code sharing proposal.
4. Optimizer hints
5. Timeout support in Derby client.
6. Grant/Revoke in Derby
7. I18 support and SQLStates for Derby client messages.
8. Updatable, scrollable result sets
9. New datatype(s) (Boolean)
10. Making FOR UPDATE optional
11. Online backup
12. XML enhancements for XPATH/XQuery support
13. setQueryTimeout for Derby client
14. ALTER Table DROP COLUMN
Satheesh
Dag H. Wanvik wrote:
"Satheesh" == Satheesh Bandaram <[EMAIL PROTECTED]> wrote:
Regarding "Long term" plans, as defined by DB project, I
wonder what other enhancements DerbyDev folks are working
on. I would like to know what else could be expected in the
next 6 months. Some of other development efforts I know
are:
1. JDBC 4.0 Stub implementation
2. Unary Plus/Minus.
3. Code sharing proposal.
4. Optimizer hints
5. Timeout support in Derby client.
6. Grant/Revoke in Derby
7. I18 support and SQLStates for Derby client messages.
You can add:
8. Updatable, scrollable result sets
We (Fernanda, Andreas and I) are making progress on making the
scrollable (insensitive) result sets updatable, stay tuned.
Dag
