Generally speaking, if you need to query the schema at runtime, you're
probably not making good use of SQL -- unless you're making some sort of
schema-agnostic general tool.
Creating a table per project is not generally a good approach. It really
doesn't let the database be a database, and may
It's a database design question, not an Android question. That's not evading
answering you -- it's probably the most helpful thing I'll tell you!
Understanding that your question really has nothing in it related to Android
will help you find the information you need, beyond anything I can tell y
Well I would put the names into a table that you can read (and maybe
some descriptive info too) but you didn't look far to find your
answer.
A quick google for "sqlite select tables" found:
http://www.sqlite.org/sqlite.htmlin there is a section "Querying
the database schema" go read that a
Well, clearly it relates to android because I'm trying to display a
list of those tables in the UI to the user, so the user could select
which one he/she wants to load. I don't think that will be in the SQL
documentation for some reason.
It is clearly an overlapping issue, but something I suspect
how is this related to Android? Read the SQLite documentation.
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-d
5 matches
Mail list logo
