Skip to content

firetable metadata organization advice #402

@weidongguo

Description

@weidongguo

When we set up firetable for a Firebase project and create a table, we start seeing metadata collections (e.g. _FIRETABLE_, _FT_USERS) created in the top level of Firestore. These metadata are mixed up with existing data generated by the users of the app

  1. Is there a way to group the metadata up (e.g. Firetable/firetable/___)?, so then all the metadata along with the data entered through the Firetable CMS is organized into one spot.

  2. If the answer is no for 1), then for separation of concern, do you recommend creating a separate Firestore instance (i.e. separate Firebase project as Firebase doesn't support more than one firestore instances right now) for data entered through the Firetable CMS?

  3. any other suggestions in separating the data generated by Firetable CMS and data generated by users through the app?

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions