Saving with ID

[trurl-master]

Hi!
Is there a way to create a cell with id?

What i expected, because it's mimicking propel:

var myBook = bookstore.books()
    .setId(1)
    .setTitle('Cold Winds')
    .save();

But that obviously not the way how it works now.

Temporarily i added a method named create that just sends record as POST request instead of PUT, so i do:

var myBook = bookstore.books(1)
    .setTitle('Cold Winds')
    .create();

It works fine, but maybe there is a better way?

Thanks!

[JASchilz]

Acknowledged! Not yet. I didn't know that Propel allows you to specify an ID on creation, and I would also like the code to support it.

In terms of the HTTP API, I'd like to handle this scenario with a PUT request: it's an appropriate verb for creating a new resource in a known location.

In terms of the JS library, I see that it could be difficult for the programmer to specify whether they want to update a record (PATCH) or create a new record (PUT). I've got a preference against having different methods for creating and updating, but it looks like that could be the right way.

Lemme think through the consequences. I'll probably write the code.

[trurl-master]

Actually, the problem arose from the fact that I wasn't able to do composite primary keys or non-ID primary keys with PropelJS, apart from that I don't see any good scenario where you'd want to set an ID on creation. So I had to rewrite the whole resourceId thing replacing it with more complex primaryKey thing, which led to some more questions, I'll create another issue on the subject.

In terms of the JS library, I see that it could be difficult for the programmer to specify whether they want to update a record (PATCH) or create a new record (PUT). I've got a preference against having different methods for creating and updating, but it looks like that could be the right way.

That what I thought, adding create method. If you know the location you can either POST (editing the record) or PUT (replacing/creating the record) and on the library level, you can't know whether the record already exists to choose the correct method.