djangoldp_source does not exist in postgres

Traceback (most recent call last):
  File "/home/sib/.local/lib/python3.6/site-packages/django/db/backends/utils.py", line 64, in execute
    return self.cursor.execute(sql, params)
psycopg2.errors.UndefinedTable: relation "djangoldp_ldpsource" does not exist
LINE 1: ...."urlid", "djangoldp_ldpsource"."federation" FROM "djangoldp...

added BUG label

changed the description

By Plup on 2019-10-26T15:09:21 (imported from GitLab project)

The database is empty...

By Plup on 2019-10-26T15:15:07 (imported from GitLab project)

This error pops on the migrate command...

By Plup on 2019-10-26T15:19:00 (imported from GitLab project)

assigned to @bleme and unassigned @jbpasquier

By Plup on 2019-10-26T15:36:18 (imported from GitLab project)

@bleme this error comes on a change you asked (I can't find the ticket anymore): https://git.happy-dev.fr/startinblox/devops/sib/commit/ee83df92efbc922feb345d61284854703629180f

I'm reverting this change.

By Plup on 2019-10-26T15:38:09 (imported from GitLab project)

@plup Nice finding, effectively automatic sources creation can't be done at this time as the database does nos exists.

Two possibilities here:

• Change this line after the first migration
• Or move it to a management command that have to be launched after migration.

@jbpasquier I don't really understand why we need to create local sources in the local database. We had said that they should be added logically on display time instead. Why did we change that?

Maybe this has changed recently. The ticket was pending for a long time. I just saw it recently and implemented it.

By Plup on 2019-10-26T16:11:41 (imported from GitLab project)

This was the original ticket: https://git.happy-dev.fr/startinblox/devops/sib/issues/67

By Plup on 2019-10-26T16:16:15 (imported from GitLab project)

@sylvain Nothing moved here, before today I didn't even know that we had an automated source creation this way.

Yes I know, but we need to discuss that as well.

ping @balessan so that you know that a lot of things went our of control on this server!

Should I close this ticket for now ? Or give it to somebody else ?

By Plup on 2019-10-26T17:19:54 (imported from GitLab project)

assigned to @jbpasquier and unassigned @bleme

For now keep use djangoldp without automatic source creation. I take it, we'll see next week how to fix that, thanks.

We need to specify if the source should be created in database, or programmatically on render.

I am not sure of what you mean by "programmatically on render". Which "rendering" are we talking about ?

the API rendering. Either we can create the local sources in the database, or we can automatically add it in the rendered JSON. I think we'd have less trouble with the latter.

assigned to @christophehenry and unassigned @jbpasquier

mentioned in commit 263ef444

By Christophe Henry on 2019-12-03T10:44:52 (imported from GitLab project)