[Oracle 9i Lite] Request for Windows CE 3.0 PowerPC 821 release

Question

After 10 days, we have unfortunately received no answer to our request mails.
We try an ultimate post in this forum, hoping that Oracle representatives are watching AND answering.
Laurent PICARD
<[email protected]>
Dear Oracle Development Team,
Hitachi & Cytale are launching a project with the INSEE (National Institute of Statistics and Economic Studies), to equip their enquirers with a mobile platform (the Cybook Pro), to update national databases on a daily basis (e.g. the French Consumer Price Index).
The INSEE considers integrating Oracle 9i Lite solution into their software architecture.
Before moving developments any further, we need to know:
- whether you are willing to compile Oracle 9i Lite for our platform;
- if so, when the release can be expected for tests and development.
Notes:
- The Cybook Pro runs Windows 3.0 on a PowerPC 821 (PPC821).
- The ODBC module of Oracle 9i Lite will be used.
- If needed, we can provide you with a PPC821 SDK.
- We (Cytale & INSEE) are willing to help if tests need be done.
- The INSEE will have their choices finalized by the end of May, feasibility and development tests must be fully completed before that date.
Companies working on the project are:
- Hitachi <http://www.hitachi.fr>
- INSEE <http://www.insee.fr>
- Cytale <http://www.cytale.com>
We are looking forward to hearing from you as soon as possible.
Best regards,
Laurent PICARD
<[email protected]>

Answer 1

This is caused by a bug in Oracle's ODBC API for Windows CE in
the dbaccess.cpp header file. It can be fixed by doing the
following;
at (or about) line 155;
Inside For Loop, before
'if(::SQLGetData' statement.
memset(&g_szBuff, 0, sizeof(g_szBuff));
This will reset the memory for the data column after it has been
read.
Oracle would have to implement this fix and then recompile mSQL
in order for mSQL to display NULL values correctly.
Cheers,
Allen.
>
Actually the problem is not (only) in mSQL as we are using the
API to view the data and are seeing the same result. We suspect
the problem is in the API which mSQL is probably also using to
access the data.
Allen.