Composite primary key breaks if null about forest-express-sequelize HOT 8 CLOSED

@arnaudbesnier I mainly expect to be able to click on the record in forest and see the detail view 🙃

The issue is just the incompatibility between forest and forest-express-sequelize in this scenario. Putting null in the URL seems reasonable AFAICT.

from forest-express-sequelize.

We'll add an issue to fix in our next sprints.
I'll let you know once fixed.

Thank you for the feedback!

from forest-express-sequelize.

Hi @aldendaniels,

I guess you would expect that:

record/451836/fielda-fieldb-null/details

to be

record/451836/fielda-fieldb-/details

right?

from forest-express-sequelize.

@aldendaniels we've investigated the issue you have. One thing that we'd like to know is your database type (Postgres, MySQL, MSSQL, ...).
Actually "real" composite primary keys cannot contain null values (at least on Postgres and MySQL).

Maybe you've defined some primary keys in you Sequelize model that are a primary key column in the database. Am I wrong?

from forest-express-sequelize.

@arnaudbesnier I'm using Postgres. You appear to be correct! The column was marked as a primary key in the ORM, but it's not actually a primary key. Thanks for the help!

I created the model using lumber, which seems to have incorrectly identified the primary keys, but that would be a separate issue

from forest-express-sequelize.

Yes it is a know issue about Lumber: ForestAdmin/lumber#85.

from forest-express-sequelize.

We have a added some code for protection in case of database/ORM different PK configuration.

from forest-express-sequelize.

Fixed on the version 1.3.5

from forest-express-sequelize.