Honestly if you are removing and adding records just use a DB that is what they are made to help achieve.
That being said I've found the limits in there past to be 50k records not based off memory footprint but more based off performance though was doing joins. Joins are much slower/complex certainly not as simple as a single table scan like you would be doing, so your millage will most certainly vary. Adam On Tue, Jun 16, 2009 at 10:20 AM, mwkorver <[email protected]> wrote: > > I have an application where I need to authenticate requests - login/ > password pair, plus a check on remote_host. If successful, the app > just passes back a signed string for use with Amazon S3. This is the > only app that this server will be running. The minimal methods I need > for this service would then be addlogin, deletelogin. > > I anticipate something on the order of 10,000 rows on this table. > Would it be too much to expect to be able to do this just using > openbd's query on query capability? I was thinking just using H2, but > realized that I really didn't need that much horsepower and I could > keep it much simpler. > > Anybody here have experience with how far you can go with this? what > is a big row count for an application.query object? > > > > --~--~---------~--~----~------------~-------~--~----~ Open BlueDragon Public Mailing List http://groups.google.com/group/openbd?hl=en official site @ http://www.openbluedragon.org/ !! save a network - trim replies before posting !! -~----------~----~----~----~------~----~------~--~---
