Create API for new tables created (issue #42)

[chuckume]

Once table are created (see issue #42), create an API so front end can insert and read the data.

[hydrandt]

I suggest we continue to use postgraphql.

@chuckume, as part of doing changes, could you please move the tables which are to be accessible via the API to a new schema called "api", so that we can have postgraphql watching over the database in that schema only?

Also I suppose we should drop the default schema and create one more for the backend database.

The steps would then be:

• [ ] create the new schemas, databases, tables
• [ ] migrate data from old tables
• [ ] make pipeline-processor, postgresql-bridge and postgraphql use the new schemas/tables
• [ ] drop the "public" schema

[chuckume]

@hydrandt What is the difference between the "backend" part and the "api" part, and how we decide which table goes where ?

[hydrandt]

The api schema will contain the data that need to be accessed via the api - postgraphql will be pointed only on this schema. So the incoming data and everything else that doesn't have to be accessible via the api should be in the backend schema.