I think the best course for a new project is to start simple, go with
sqlite, if you find you need more performance or some particular
feature, bump up to postgresql. mysql is pretty common, but there are
concerns about its future under oracle. That said, there’s no shortage
My concern is - Does “Sqllite3” capable of storing 30000 rows in each
table? I will use it in my internal projects.
My concern is - Does “Sqllite3” capable of storing 30000 rows in each
table? I will use it in my internal projects.
If you want to adopt a database engine, you’d better read some of the
documentation that comes with it. For example, look at the last item
in this page:
Thank you very much! That’s the information I was looking from you like
experienced people.
If it’s just 30,000 items then Marshal or PStore might do as well. If
the whole data set easily fits into memory that would probably be the
easiest choice. Sample:
$ time ruby -e ‘h={};30_000.times {|i|
h[i]=10.times.map(&:to_s)};t=Time.now;File.open(“x”,“wb”){|io|Marshal.dump(h,
io)};puts(Time.now-t)’
0.3430196
If it’s just 30,000 items then Marshal or PStore might do as well
Note PStore really sucks because it rewrites the entire database every
single time you mutate it. It’s about the most brain dead persistence
model
ever.
On Thu, Jan 31, 2013 at 11:50 PM, Robert K. [email protected]
wrote:
If it’s just 30,000 items then Marshal or PStore might do as well
Note PStore really sucks because it rewrites the entire database every
single time you mutate it. It’s about the most brain dead persistence model
ever.
It’s a tool. There are use cases where it’s appropriate and others
where it’s not. That has nothing to do with “brain dead”. The
approach to serialize objects is actually quite common in various
programming languages.
I think the best course for a new project is to start simple, go with
sqlite, if you find you need more performance or some particular
feature, bump up to postgresql. mysql is pretty common, but there are
concerns about its future under oracle. That said, there’s no shortage
My concern is - Does “Sqllite3” capable of storing 30000 rows in each
table? I will use it in my internal projects.
It might depend on how many tables, how many fields in each table, and
how much information is in each field, being used in a single
application. That said, sqlite is quite capable. Where sqlite tends to
fall down is when you have very complex relationships between tables
with many inserts/updates; and THAT said, that’s where most databases
start to degrade in performance anyway, unless you’re really good at
designing them AND understand how to do the SQL.