J. R. Westmoreland <j...@...> writes:
>
> Can someone tell me how many tables a given database can hold.
>
> I'm looking at an initial design of an application that could have a table
> of data for each city in a state. This could be possibly more than a
> thousand tables.
>
> With that many tables how would the performance of the database be effected?
>
> Thanks,
>
> J. R.
As others have observed, this is an unwise design, not least that any code
written will have to 'edit' in the city table name by program rather than
having it manipulable by SQL statements and 'bound' values.
Like sets of items ("entity/relationship sets") should go into the
same table with a column/field value to distinguish the instances.
You can easily say "... WHERE City='Boston' ..." or whatever.
Another way of putting this is that separate tables should not
usually be used just to group sets of otherwise
identically-structured data records.
Search keywords: database schema design entity relationship
Regards,
MikeW
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
