Custom IDs about sequelize HOT 5 CLOSED

Hey there,

someone just submitted a pull request for that issue. AFAIK it's not fully working yet, but you might want to try it. I hadn't enough time to test it yet, but will probably do on the weekend.

https://github.com/sdepold/sequelize/pull/47 (can you see the content on that page??)

The guy just closed the pull request due to some bugs. But he want to fix them on weekend.

from sequelize.

That's something but if I understand the patch well the columns which compose the composite ID key are still supposed to be integers I was more looking forward doing something like this in a model declaration:

id: { type: "VARCHAR(64)", primaryKey: true }

If I have some time over the week-end and nobody haven't figured it out 'til then I'll look into it...

from sequelize.

hey there. i'm going to support the primaryKey-thing in the rewrite-version of sequelize. if you want to you can take a look at https://github.com/sdepold/sequelize/blob/rewrite/test/Sequelize/define.js

but at the moment there aren't any documentation. and associations are missing too :)

from sequelize.

OK here are some lines of testcode, which might be interesting for you:

https://github.com/sdepold/sequelize/blob/rewrite/test/Sequelize/define.js#L30
https://github.com/sdepold/sequelize/blob/rewrite/test/Sequelize/define.js#L36
https://github.com/sdepold/sequelize/blob/rewrite/test/Model/find-findAll-all.js#L63

At this very moment, the rewrite version allows you to specify an attribute as primary key using the flag primaryKey: true.
If one primaryKey is defined manually, sequelize will not add an id column. Please let me know, what you think and if that solves your problem.

from sequelize.

Hmm, I will check that out over the week-end cause I have a pretty busy week but seems after a quick look that seems to be the thing ;).

from sequelize.