Home arrow static arrow Java Programming [Archive] - CallableStatement in 1.5 and 1.4
Warning: Creating default object from empty value in /www/htdocs/w008deb8/wiki/components/com_staticxt/staticxt.php on line 51
Java Programming [Archive] - CallableStatement in 1.5 and 1.4
1 Duke Stars available
This topic has 17 replies on 2 pages.    « Previous | 1 | 2 |

Posts:27,518
Registered: 11/3/97
Re: CallableStatement in 1.5 and 1.4  
Jun 22, 2004 4:21 PM (reply 15 of 17)



 

COM mandates that if you change a COM interface for
any reason than the GUID that represents it must
change as well.

Sorry but I have no idea what this specific interface for a specific OS has to do with this discussion.
 

Posts:3,999
Registered: 00-05-26
Re: CallableStatement in 1.5 and 1.4  
Jun 22, 2004 7:36 PM (reply 16 of 17)



 
My point is that COM believes that an interface, once published, is unchangeable.

I would agree. To me it is just sloppyness on sun's part. Luckily, there aren't alot of folks who implement JDBC interfaces, and so they get away with not having public hysteria.

Imagine 1.5 finally rolls out, and ActionListener was now

public interface ActionListener{      public void actionPerformed( ActionEvent ae );      public void logActions( Map<String> logEntries );}


yes it's silly, but it's exactly what they did with CallableStatement. You'd have code that you had written previously that is now unable to be compiled, or compilable on both 1.4 and 1.5.

It's only that you don't give a pile about implementing CallableStatement that it seems minor.
 

Posts:27,518
Registered: 11/3/97
Re: CallableStatement in 1.5 and 1.4  
Jun 23, 2004 9:13 AM (reply 17 of 17)



 
My point is that COM believes that an interface, once
published, is unchangeable.

That isn't exactly true.

What happens is that they publish a second interface.

And your users must still struggle with what to do when they want to use the newer interface and you do not support it.

I would agree. To me it is just sloppyness on sun's
part. Luckily, there aren't alot of folks who
implement JDBC interfaces, and so they get away with
not having public hysteria.

I suppose. As I said the older implementations work with the newer interface. You just can't call the methods that are not implemented.

Imagine 1.5 finally rolls out, and ActionListener was
now

public interface ActionListener{public void actionPerformed( ActionEvent ae );public void logActions( Map<String> logEntries );}


yes it's silly, but it's exactly what they did with
CallableStatement. You'd have code that you had
written previously that is now unable to be compiled,
or compilable on both 1.4 and 1.5.

I did provide solutions for that problem.

And the users of your library (which jdbc drivers are) probably don't care if you (as the library developer) have problems compiling the library. They just want a version that works with whatever they are doing.

It's only that you don't give a pile about
implementing CallableStatement that it seems minor.

Not sure what you mean about that.

From my point of view it simply doesn't matter because 1.5 wont be stable probably until sometime next year. So production systems that I work on won't even start conversion/test until then. And it is really unlikely that I will be using the method that you are having problems with (I doubt I use anything that wasn't in JDBC 1.0.) So as long as the drivers that I use are compliant with JDBC 2.0 the stuff in JDBC 4.0 matters little to me.
 
This topic has 17 replies on 2 pages.    « Previous | 1 | 2 |