rom-relation | This is an old ROM prototype | Video Game library

Tried to implement the Cloud data-flow task, loading data from PostgreSQL database table to Google Cloud Bigquery table help of below URL document. When executing data-flow job got issue. Refer the screen shot 1.

URL: Approach 2:ETL into BigQuery with Cloud Dataflow

Screen Shot of error message

I am currently building a loopback project and I need to discover existing data in a PostgreSQL database to make my models, I have successfully created the models by following the tutorial found in the docs: https://loopback.io/doc/en/lb3/Discovering-models-from-relational-databases.html#discover-and-save-model-definitions , but when I run GET method for any model I get an error that says

relation "public.acl" does not exist

can anyone help me fix this issue, Thanks in Advance.

I am writing an assignment system for radio newscasts. The data tables:

This question pertains specifically to LoopBack Node.js Framework from StrongLoop (owned by / backed by IBM). From what I know so far this should be a two step process.

1. Write a script to discover / create Models from the existing MySQL Schema. Here are the official docs regarding that: https://loopback.io/doc/en/lb3/Discovering-models-from-relational-databases.html

I think I successfully handled the discovery / model creation piece using the following NPM package: https://www.npmjs.com/package/loopback-discovery (GitHub repo for project can be found here: https://github.com/akera-io/loopback-discovery)

1. Use AutoUpdate (via script in loopback-project/server/boot directory) to check to make sure the MySQL DB fits with the Model definition that was created by the Discovery / Creation module. Here is a StackOverflow topic on the difference between LoopBack's AutoMigrate and AutoUpdate functions: loopback automigrate vs autoupdate

From there I think I should be able to hit my API and access the data in the MySQL datasource, but alas...

When I go through the above steps, I successfully get ALL of the models from my selected table in the loopback-project/common/models directory (my models happen to be posts from a blog).

In my loopback-project/server/model-config.json all of the tables / models from my MySQL database exist and I then set my "posts" model to public in order to expose it via API.

Since the NPM Module discussed above uses LoopBack and the LoopBack datasources I know that I can connect to my DB and my loopback-project/server/datasource.js file properly configures loopback to talk to my server / mysql instance.

When I launch my loopback instance using node . I can hit http://0.0.0.0/explore and I have the proper CRUD options for my 'Posts' model exactly as I would expect.

HOWEVER.

When I attempt to query my DB via GET Posts Api Endpoint I receive the following error that my table does not exist (even though it clearly does in MySQL since my blog is using it AND the previous NPM package was able to read from it:

Following Loobback Docs: Discovering models from relational databases, Stackoverflow answer: Loopback not discovering models and Loopback datasource juggler API: Datasource I created a discover js script to get models from an oracle database. The problem is that it never managed to read the relations from the tables. I used the methods

• discoverAndBuildModels - The result object had the properties of the table and an array called relations but that array was empty
• discoverSchema - I managed to get the actual model JSON file and write it to the appropriate location. As the method is described in the api to not read relations i was not surprised to not find any here
• discoverSchemas - Includes option to read relations (called relations but also tried it with associations) which gave me a similar result than discoverSchema but the "relations" tag only had an empty json object assigned to it.

I tried all options with a variety of relations and associations settings but none of them gave me anything but an empty object as the "relations" tag.

Am I missing something in the setup?