> What is better performance of the Django, Sqlite3.
> Have 20.000 entrances in the table with 1000 columns
> or 2.000.000 entrances in the table with 10 columns
I would hate to work with a 1000 column table. and row-oriented
databases (like all traditional SQL ones) typically assume that a
single row is an easily manageable amount of memory.
Also, most data normalization rules tend to reduce the amount of
columns per table, even at the expense of more tables or more records.
If there's any regularity on those 1000 'lines' they shouldn't be a
column each.
finally, 2x10^6 records is not a big number for any database.
so, i wouldn't even consider the option of adding columns to reduce
records. definitely go with as few similar columns as possible. Even
10 columns are too many if they're similar. Much better would be
20'000,000 records with just a single 'line' each.
--
Javier
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
No comments:
Post a Comment