InstantDB Project
About InstantDB
Project Mail Lists
Short History
Reporting Bugs
Screen Shots
3rd Party Examples
FAQs

Software
Downloads
Documentation
CVS Repositories
Roadmap
License

About Enhydra.org
Who We Are
News, Articles & Events
Getting Involved
Contact Us

Community
Demos
Contributions
Resources
Case Studies
On The Edge! -NEW-
Commercial Vendors

Doug

An indexed lookup, testing for equality,  will run at probably the same
speed regardless of the data type. InstantDB uses hash indexes instead of
b-trees so all comparisons are integer comparisons.

How big is the table and how slow is the lookup?

Regards

Pete

--

Peter Hearty                         peter.hearty@lutris.com
Lutris Technologies (UK)        http://www.lutris.com
----- Original Message -----
From: "Doug Robinson" <drobinson@zicorp.com>
To: <instantDB@enhydra.org>
Sent: Friday, January 12, 2001 8:50 PM
Subject: InstantDB: how to make it faster


> Hello
>
> I have an InstantDB database running on a Cassoiopeia. (a pocket PC)
> I do a simple select on a indexed column. This column is always
> (or can be make so) a 2 character string.
>
> Would it be faster to convert the string into a
> short and run the select against that. Indexed or not?
>
> Would any improvement be significant?
>
> Thanks for your time.
> dkr
> --------------------------------------------------------------------------
---
> To unsubscribe from this mailing list, send email to majordomo@enhydra.org
> with the text "unsubscribe instantdb" in the body of the email.
> If you have other questions regarding this mailing list, send email to
> the list admin at owner-instantdb@enhydra.org.
>


-----------------------------------------------------------------------------
To unsubscribe from this mailing list, send email to majordomo@enhydra.org
with the text "unsubscribe instantdb" in the body of the email.
If you have other questions regarding this mailing list, send email to
the list admin at owner-instantdb@enhydra.org.