support SELECT.forUpdate(ignoreLocked)

[kulliax]

As already described in cap-js/cds-dbs#917, we would like to use the ignorelocked function. This is already implemented and should also be made possible in ts with this pr.

[daogrady]

Hi @kulliax ,

thank you for your contribution!
Seeing that this is not mentioned in CAPire, as you found, and the linked implementation PR states "unofficial", this appears to not be part of the user-facing API and should therefore not be part of the types either.
As you appear to have need for this API, let's keep this PR open so you can approach the runtime team again and suggest to make this part of the API. If that goes through, we can gladly continue with adding it to the types as well.

Best,
Daniel

[kulliax]

added pr to doc: capire/docs#2010

[daogrady]

Hi @kulliax ,

appreciated! But it has to go the other way around: the devs make the API official, then it can be documented. It does not become official by virtue of being documented. David's comment on the implementation PR strikes me as this not being the case yet.

Best,
Daniel

[daogrady]

@David-Kunz can you please weigh in on whether this API is supposed to be official by now, or if there are plans to make it official?

[kulliax]

I really don't understand making this publicly not available. It's normal SQL, it just makes our lives more complicated in many places because we set locks in our projects.

Basically it's the same as the following snippet ... only in CQL:
await cds.db.run("SELECT ... FROM ... WHERE ... FOR UPDATE IGNORE LOCKED", [...]);

[daogrady]

Hi @kulliax ,

while I understand your demand for this functionality, our architects need to meticulously keep track of our API. This ensures that we strike the right balance between fulfilling our users' needs and being able to faithfully adhere to the underlying standards we need to cater to. I can only assume that this particular API is either not set in stone, and could therefore be reverted at some point (and thus has not become publicly available), or is scheduled for becoming part of the official API at some point. As that is not the case today, feel free to weigh in on the existing feature request on that topic (unless, obviously, if you already are involved there. 😉).

Best,
Daniel

[kulliax]

Hi @daogrady, thats my request :)

I just find it strange to implement standard functionality but not offer it to developers. Maybe someone else can comment on this and explain it.

And as for the API, it only affects SQL Services, and when I look at it, it is implemented in both Hana and Postgresql: cap-js/cds-dbs#1074