I've begun writing a native RPC connector for UniData/UniVerse and will post
something as soon as it's worthy.
slestak wrote:
>
> Norm,
>
> I have been looking at this as well. Thinking about using swig to wrap
> the Intercall library so code can be written independently of the ODBC
> driv
Norm,
I have been looking at this as well. Thinking about using swig to wrap
the Intercall library so code can be written independently of the ODBC
driver.
How far have you gotten so far. I would definitely like to help on this.
Steve
___
DB-SIG
Norman:
You did not specify what platform you will be implementing this on. I
think everyone assumes Windows.
A quick google search leads me to:
http://gigamegatech.com/2008/09/16/u2-and-adonet-relatively-relational/
which mentions that IBM has done some recent work with an ADO.NET driver.
dot
Norman Bauer wrote:
> Hello,
>
> I am beginning to dive into developing a module connecting to an IBM
> UniVerse database. I'll first start by saying that this is the largest
> undertaking I have ever had and so far the experience has been fun,
> yet frustrating at times... I know wa
>
>
On Wednesday 26 August 2009 19:20:21 Norman Bauer wrote:
>
> I am beginning to dive into developing a module connecting to an IBM
> UniVerse database. I'll first start by saying that this is the largest
> undertaking I have ever had and so far the experience has been fun,
> yet frustrating at times
On Aug 26, 2009, at 10:20 AM, Norman Bauer wrote:
Before I get into the meat of it, I would really appreciate some
general pointers in developing to the DB API, pitfalls and the likes.
DB-API 2.0 spec is pretty much all there is, AFAIK. It's pretty
straightforward...
There's also some unittes
