Cache table schema changed with Drupal 7

Hello, I think this patch is a little simpler. Rather than get the new cache_browscap schema in a different way than browscap_schema(), we can re-use browscap_schema().

Also I capitalized Browscap in the function comment for consistency with another comment in the .install.

From Updating tables: hook_update_N() functions:

Important note: You may be tempted to pass a table definition from your own hook_schema function directly to db_create_table(). Please read why you cannot use hook_schema from within hook_update_N().

;)

Makes sense. The original patch seems to be a fine way to do this, then. However, browscap_schema() is currently defining the cache table using drupal_get_schema_unprocessed(), which also causes the problem referenced in #3. This patch also changes browscap_schema() to define the cache table in the same way as the original patch, without duplicating code.

Changed function name _browscap_cache_7201() to _browscap_schema_cache_7201() for consistency with system_schema_cache_7052().

On second thought, it would probably be clearer to just duplicate code between hook_schema() and hook_update_N(). Will prepare an alternative patch.

This is Kevin Rogers' patch with an additional change:
browscap_install() is changed to also use system_schema_cache_7054() for consistency and to avoid the problem mentioned in #3. Specifically, the problem is that browscap_install() currently uses drupal_get_schema_unprocessed('system', 'cache'). If the system cache schema changes, Browscap users will have different cache schemas depending on when they installed the module, which is probably a situation best avoided.

Removed accidental blank line versus #7.

I'm closing it because the issue was created a long time ago without any further steps.

if you still need it then raise a new one.
thanks