Encouraging response, thanks.
>
>
> My gut-feeling is that for small databases, callbacks into Rexx to do the
> collation would probably work reasonably well. At what point it might
> become too slow could only be determined after implementation. And,
> really, small databases are really the applications I visualized using
> ooRexx and ooSQLite. 300, 700, 2,000 records.
>
In that case I have to disappoint (?) you. The project I'm working on is
successfully handling ten's of 1000 of rows of SQLite data with no problem.
This is why I believe that a callback routine written in Rexx would be
asking for too much, because the collation function according to the
documentation is used for all types of comparison within SQLite.
> My other thought was, that for ooSQLite it might be possible to implement
> some type of plugin function. Where you could for instance plugin a
> collation extension written in C / C++. This is probably somewhat similar
> to what you mean by (de)registration. Then if people wanted some type of
> general use collation function, someone might step in with C / C++ skills,
> write it, and make it generally available.
>
>
As far as I understand the collation function is in a way a plug-in
function in SQLite where (de)registration of the routine is done using the
sqlite3_create_collation call. What's missing is a way to dynamically load
the required routine.
Staffan
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users
