Re: SAPDB not competitive due to neglect of Win32 drivers

>>>Then maybe he shouldn't use .NET?
>>
>>What an arrogant position.
> 
> What's arrogant about "A is crap, make it better", "well maybe you should
> not use A, because there are B and C that are better".

What if SAP had decided that Java is no good? We wouldn't have such a 
fine JDBC driver :-(

> With Java you at least have several vendors to choose from if Sun turns
> out to be complete nutters, with .NET you are just screwed when microsoft
> descides that .TV is going to be the next big thing.

Well, Java is not OpenSource. Mono will.

>>Would you use the JDBC-ODBC bridge?
> 
> Why not? Were the people writing the bridge incompetent?

Not really. It's just a difficult task to code a working bridge.

>>You would expect a good  JDBC driver and fortunately we have such 100%
>>Java driver for SAPDB.
> 
> Why is that good? (well except for portability)

Well, it can directly communicate to the server and doesn't need to 
communicate with an API that itself is a "bridge" to the server protocoll.

>>Without it, i wouldn't have chosen SAPDB for my work, since a bridges
>>are often faulty and unreliable.
> 
> Why is that? Why should a bridge be more unreliable than a much larger
> piece of newly developed code?

More code, mor bugs. It's just that simple.

>>Well, we can't influence the ODBC API itself, just solve bugs within
>>SAPDB's ODBC driver. In addition you'll have to fight with the birdge's
>>bugs.
> 
> Ah so what you are saying is that SAP DB has a buggy client lib and that
> you'd like to get an improved one?

No, i just said that we cannot improve the ODBC-API since it is kind of 
a standard.

>>>I've heard mumblings of a new, modern ODBC interface being written for SAP
>>>DB, so maybe that's the answer; wait a while and see if a better driver
>>>should pop up.
>>
>>What the hell is a "modern ODBC interface" ?
> 
> One younger than me.

;-)

>>Will the SAPDB ODBC driver support a higher version of ODBC?
> 
> Dunno, but there were talk about a completely new client lib at some
> point, the current ODBC interface is grafted ontop of the old client
> interface and unfortunatly *that* part isn't quite stable.

Let's see what MaxDB will be like. I don't see that happening for SAPDB.