On Mon, Feb 23, 2009 at 3:55 AM, Quan Zongliang <quanzongliang@gmail.com> wrote:
>> Yeuch. I'm still not convinced we want to use wxODBC - it sounds like
>> it's got more issues than we knew about :-(. How much pain would be
>> involved in using ODBC directly? On Windows, everything should always
>> be available, as it should on Mac (which uses iODBC). On Linux we'd
>> need to be able to run regardless of whether iODBC (or unixODBC if we
>> supported that) was installed.
> If our code follow the ODBC standard, I think them will works fine.
> Like the wxWidgets's definition, include corresponding header files for different platform.
>
> A new compile option is needed.
I think this is the way to go. We should probably get it working on
Windows first, and then we can work together to get Mac support
working (because both of those platforms *always* support ODBC). Then
we can figure out how to deal with Linux - it may take some loose
binding magic so we can run in the absence of iODBC on that platform.
I'm not sure we need to support unixODBC as well.
>> Well, that's good for us, but not good for you if there's lot's of spare time!
> Don't worry about this. It is not because of economy crisis. ^-^
> The most of my company's projects is designed in Japan and developed in China.
> With the low-cost, our business is same as last serial years almost.
Thats good :-)
> And in our projects, always use some free frameworks or tools which coded by java.
> Sometimes them need be modified in order to support Japanese or Chinese.
> Most was done by me.
> But I would like to do something with C or C++.
> So after discussion with my boss, I got permission.
Excellent :-D
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com