on 3/9/00 1:40 PM, christopher baus <[EMAIL PROTECTED]> wrote:
> I will say no, because of village's heavy dependency on metadata. I've
> tried it. I looked at the code in the freeTDS driver for the metadata
> support. It is all stubbed out. Actually it throws an exception when the
> user attempts to access metadata. Of course it you want to use SQL server
> as data source you can write your own access code that doesn't use village
> of metadata. But really the only Turbine code you could use in that case is
> the connection pooling.
>
> Based on my limited knowledge of TDS it doesn't seem easy to implement
> metadata support. It seems that this stored procedure implementation in
> jConnect probably requires two requests and doesn't actually retrieve the
> info from the TDS stream.
Turbine's db connection pool will work with ALL JDBC drivers. The design of
it makes it easy to support this. As for Village, there is no reason why you
have to use Village within Turbine.
-jon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
