Create on a model without id about loopback-connector-oracle HOT 8 CLOSED

LoopBack assumes that there is always a PK. It's required for a lot of APIs to be functional. Is there a reason that your table cannot have a PK?

You can also fake a PK by adding id: true to one of your property definitions.

from loopback-connector-oracle.

I'm working on an existing database that doesn't have PK for some reasons and that I can't modify. There are some unique constraints that I could use as PK, but there is nothing related to unique constraint in model.definition.properties[propertyName]. Is there a way to know in the generated model where the field with unique constraint is?

Thanks.

from loopback-connector-oracle.

Do you use discovery to build loopback models from oracle tables?

You can always nominate a property as an id (pk) in loopback by setting id to true. It doesn't require a DB PK.

Sent from my iPhone 5

On Jul 16, 2014, at 1:02 AM, vbourgeois [email protected] wrote:

I'm working on an existing database that doesn't have PK for some reasons and that I can't modify. There are some unique constraints that I could use as PK, but there is nothing related to unique constraint in model.definition.properties[propertyName]. Is there a way to know in the generated model where the field with unique constraint is?

Thanks.

—
Reply to this email directly or view it on GitHub.

from loopback-connector-oracle.

Yes I use the "discoverAndBuildModels" method, but it doesn't seem to get the unique constraints I want to use as PK. Does it matter if I select a random property as PK or it will add constraints on it in loopback?

from loopback-connector-oracle.

I finally found a way to identify the eligible column for primary key.

Model is built with discoverAndBuildModels and I tried to set the PK manually like this: model.definition.properties[idName].id = true;.
But it's not working, dataSource.idName(modelName); still returns undefined and causes the create method to fail.

How can I set the PK manually?

from loopback-connector-oracle.

Can you do the following?

model.definition.rawProperties[idName].id = true;
model.definition.build(true); // Force rebuild the list of properties

from loopback-connector-oracle.

It's working, PK is set and create method works.
Thank you.

from loopback-connector-oracle.

I am working with a mongo db collection called users with the following fields : _id (default mongo created pk field), email, username, status.
I have created a model where I have marked email field as the id field. But after going through the full cycle when i run the get query for /users/{id} loopback queries only the _id field but doesnt query the email field (which I have marked as the id field in my model). Can someone help me in changing this?

Thanks

from loopback-connector-oracle.