Hi,
Daniel == Daniel John Debrunner [EMAIL PROTECTED] wrote:
Daniel This would be great to be on a wiki page, including links to the Jira
Daniel entries with the functional specs. I'm losing track of which functional
Daniel specs are out there, just saw in some reply that Dag has posted a
I like Lance's suggestion and would like to propose it as a general
policy. I think that this will handle Army's XML work as well as the
other new 10.2 datatypes:
If you add a new datatype to a server release (e.g., BOOLEAN or XML),
then you must specify the following:
1) A legacy datatype
Rick Hillegas wrote:
I like Lance's suggestion and would like to propose it as a general
policy. I think that this will handle Army's XML work as well as the
other new 10.2 datatypes:
If you add a new datatype to a server release (e.g., BOOLEAN or XML),
then you must specify the following:
Rick Hillegas wrote:
I like Lance's suggestion and would like to propose it as a general
policy. I think that this will handle Army's XML work as well as the
other new 10.2 datatypes:
If you add a new datatype to a server release (e.g., BOOLEAN or XML),
then you must specify the following:
Daniel John Debrunner wrote:
Rick Hillegas wrote:
I like Lance's suggestion and would like to propose it as a general
policy. I think that this will handle Army's XML work as well as the
other new 10.2 datatypes:
If you add a new datatype to a server release (e.g., BOOLEAN or XML),
then
Rick Hillegas wrote:
Daniel John Debrunner wrote:
Maybe replace 'you must' with 'you can'. If someone has the itch to add
a type for embedded only, then I don't think they should be forced to
make it work with old or new clients.
I'm concerned that if you can create a column, you ought
Satheesh Bandaram wrote:
Hi Rick,
Rick Hillegas wrote:
We will probably have to collaborate here. If you select an XML
column, the ResultSetMetaData needs to say that the column is of type
java.sql.SQLXML. This, at least, was the consensus of the community
which prevented me
Satheesh Bandaram wrote:
list of potential 10.2 features
This would be great to be on a wiki page, including links to the Jira
entries with the functional specs. I'm losing track of which functional
specs are out there, just saw in some reply that Dag has posted a
functional spec on RowId (I
OK.. I will work on getting this info on a Wiki.
Satheesh
Daniel John Debrunner wrote:
Satheesh Bandaram wrote:
list of potential 10.2 features
This would be great to be on a wiki page, including links to the Jira
entries with the functional specs. I'm losing track of which functional
specs
Hi Army,
Some additional comments follow. Cheers-Rick
Army wrote:
...
That said, I spent some time looking at this more and I tend to agree
with you about moving the logic to the network layer: it does some
cleaner to do it that way, as that will allow the server to recognize
the XML
Hi Rick,
Rick Hillegas wrote:
We will probably have to collaborate here. If you select an XML
column, the ResultSetMetaData needs to say that the column is of type
java.sql.SQLXML. This, at least, was the consensus of the community
which prevented me from re-enabling the BOOLEAN datatype a
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
Hi Army,
Some more comments follow. Cheers-Rick
...
Ah, okay, I had a feeling that JDBC 4.0 was where you were headed :)
I agree there is a need for this, and I'm glad you're looking at
getting the 4.0 machinery in place. Note that, in the meantime, I am
working on a pre-JDBC 4.0
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,
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
Hi Rick,
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
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.
JDBC 4.0 Stub implementation
Unary Plus/Minus.
Code sharing proposal.
Optimizer hints
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
Rick Hillegas wrote:
Here are the datatypes I want to add, re-enable, or extend in the
10.2 timeframe:
[ snip ]
SQLXML
How would this (the SQLXML type) differ from the existing XML type available
as of 10.1.1 (DERBY-334)?
Army
Hi Army,
I would like to hook the XML type up to the network layer and the JDBC
4.0 machinery. Currently, you cannot select an XML column and return it
to the client. Nor can you insert directly into an XML column. I would
like to make the compiler accept the following statements:
select
Rick Hillegas wrote:
I would like to hook the XML type up to the network layer and the JDBC
4.0 machinery.Currently, you cannot select an XML column and return it
to the client. Nor can you insert directly into an XML column. I would
like to make the compiler accept the following statements:
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
22 matches
Mail list logo
