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 be very inefficient for creating/deleting projects, doesn't give you the referential integrity that you'd get with a foreign key constraint, etc. Still, knowing how to examine the schema is a very useful skill during development! -- 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-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
