SQL Anywhere ultralite - Runtime library for embedded SQL on PalmOS Dev Suite

Author

Runtime library for embedded SQL on PalmOS Dev Suite

David Zuiker

2005-10-27, 7:41 am

Hi,

I am developing a PalmOS application using Palm OS developer suite. I have
the developer edition of SQLAnywhere and I am trying to incorporate an
ultralite database.

The application has been successfully built and runs, as long as I don't
embed any SQL. The preprocessor and ulgen steps run fine, and I have
included their outputs in the build. However, when I include the code
warrior version of the runtime library (the only one available, as far as I
can see, for this platform), the build process fails saying that the file
format of the library is not recognized.

Alternatively, if I don't include the runtime library, I get build errors
like

"undefined reference to 'ulpp_dbinit'"

and so on for all of the database calls generated by the preprocessor.

If you can tell me what I have to include or link to supply the correct
references for these, I would really appreciate knowing.

Thanks,

Dave

David Fishburn

2005-10-27, 7:41 am

"David Zuiker" <davidz_@hotmail.com> wrote in
news:4342f815$1@foru
ms-1-dub of sybase.public.sqlanywhere.ultralite:

....
DZ> The application has been successfully built and runs, as long as I
DZ> don't embed any SQL. The preprocessor and ulgen steps run fine, and
I
DZ> have included their outputs in the build. However, when I include
the
DZ> code warrior version of the runtime library (the only one available,
DZ> as far as I can see, for this platform), the build process fails
DZ> saying that the file format of the library is not recognized.

If you are just beginning, I would not use the static UL API, you should
be using the Dynamic SQL API. The static is being removed going
forward.

See from the 902 docs (which you should be at as a minimum):
UltraLite Database User's Guide
Dynamic SQL
Introduction to dynamic SQL

and

UltraLite Database User's Guide
Developing Applications for the Palm OS

Then fire away with some more questions.

--
David Fishburn
Certified ASA Developer Version 8
iAnywhere Solutions - Sybase
Professional Services
Please only post to the newsgroup
Please ALWAYS include version and MORE importantly BUILD number with
EACH post (dbeng9 -v).

EBFs and Maintenance Releases
http://downloads.sybase.com/swx/sdmain.stm

Developer Community / Whitepapers
http://www.ianywhere.com/developer

CaseXpress - to report bugs
http://casexpress.sybase.com

CodeXchange - Free samples
[url]http://ianywhere.codexchange.sybase.com/servlets/ ProjectDocumentList[
/url]

Tim McClements

2005-10-27, 7:41 am

As you have discovered, UltraLite only supports codewarrior development for
Palm. The Palm OS developer suite uses the PRCTools compiler to target 68k
and we do not support this compiler. PRCTools' lack of support for large
data segments tends to make UltraLite development unpractical.

- Tim

"David Zuiker" <davidz_@hotmail.com> wrote in message
news:4342f815$1@foru
ms-1-dub...
> Hi,
>
> I am developing a PalmOS application using Palm OS developer suite. I
> have
> the developer edition of SQLAnywhere and I am trying to incorporate an
> ultralite database.
>
> The application has been successfully built and runs, as long as I don't
> embed any SQL. The preprocessor and ulgen steps run fine, and I have
> included their outputs in the build. However, when I include the code
> warrior version of the runtime library (the only one available, as far as
> I
> can see, for this platform), the build process fails saying that the file
> format of the library is not recognized.
>
> Alternatively, if I don't include the runtime library, I get build errors
> like
>
> "undefined reference to 'ulpp_dbinit'"
>
> and so on for all of the database calls generated by the preprocessor.
>
> If you can tell me what I have to include or link to supply the correct
> references for these, I would really appreciate knowing.
>
> Thanks,
>
> Dave
>
>

Tim McClements

2005-10-27, 7:41 am

But note that ESQL will be supported going forward, so it's still a fine
choice of API. As David mentioned, UltraLite will no longer statically
generate the database code using the analyzer (sqlpp/ulgen); instead, only
the sqlpp preprocessor will be used before linking to the UltraLite runtime
library.

- Tim

"David Fishburn" <fishburn_spam@off.ianywhere.com> wrote in message
news:Xns96E65BCF7FAE
Efishburnsybasecom@1
27.0.0.1...
> "David Zuiker" <davidz_@hotmail.com> wrote in
> news:4342f815$1@foru
ms-1-dub of sybase.public.sqlanywhere.ultralite:
>
> ...
> DZ> The application has been successfully built and runs, as long as I
> DZ> don't embed any SQL. The preprocessor and ulgen steps run fine, and
> I
> DZ> have included their outputs in the build. However, when I include
> the
> DZ> code warrior version of the runtime library (the only one available,
> DZ> as far as I can see, for this platform), the build process fails
> DZ> saying that the file format of the library is not recognized.
>
> If you are just beginning, I would not use the static UL API, you should
> be using the Dynamic SQL API. The static is being removed going
> forward.
>
> See from the 902 docs (which you should be at as a minimum):
> UltraLite Database User's Guide
> Dynamic SQL
> Introduction to dynamic SQL
>
> and
>
> UltraLite Database User's Guide
> Developing Applications for the Palm OS
>
>
> Then fire away with some more questions.
>
> --
> David Fishburn
> Certified ASA Developer Version 8
> iAnywhere Solutions - Sybase
> Professional Services
> Please only post to the newsgroup
> Please ALWAYS include version and MORE importantly BUILD number with
> EACH post (dbeng9 -v).
>
> EBFs and Maintenance Releases
> http://downloads.sybase.com/swx/sdmain.stm
>
> Developer Community / Whitepapers
> http://www.ianywhere.com/developer
>
> CaseXpress - to report bugs
> http://casexpress.sybase.com
>
> CodeXchange - Free samples
> [url]http://ianywhere.codexchange.sybase.com/servlets/ ProjectDocumentList[
/url]
>

David Zuiker

2005-10-27, 7:41 am

> If you are just beginning, I would not use the static UL API, you should
> be using the Dynamic SQL API. The static is being removed going
> forward.

Is this possible in C? I have been researching it, but it seems that the
only option open to C developers is the static API.

Thanks,
Dave

Michael Thode

2005-10-27, 7:41 am

We also support a subset of the ODBC interface, but I'd only suggest using
that if you already have a significant investment in ODBC code.

I'd like to emphasise what Tim mentioned in his post, ESQL is not going away
and shouldn't be considered a deprecated interface. Its true that static UL
is being deprecated, but static ESQL will be replaced with dynamic ESQL in
our jasper release. If you upgrade to Jasper in the future you should find
the transition straight forward.

Mike

"David Zuiker" <davidz_@hotmail.com> wrote in message
news:43443c44@forums
-2-dub...
>
>
> Is this possible in C? I have been researching it, but it seems that the
> only option open to C developers is the static API.
>
> Thanks,
> Dave
>
>

Sponsored Links