Does Yugabyte provide "select for" grammar for YSQL? If not, any plan or release ETA?
I have looked at the docs, it doesn't seem support one


While Postgres 11 is ...

Thank you, you guys built amazing products!
EDIT 1: Add current (27/07/2019) yugabyte select support docs
Thanks for the question @incubus8! SELECT FOR has a dependency on [#1199] [YSQL] Support locking options in SELECT statement (SELECT FOR UPDATE etc.)
@m-iancu or @ndeodhar would be the best folks to answer if there are any additional dependencies on top of the one above.
Thank you, you guys built amazing products!
Glad you like it 馃檹
Hi @incubus8, glad to hear that you like YugaByte DB!
We're going to start working on locking options for SELECT soon and plan to do it in two phases:
FOR SHARE and FOR KEY SHARE: This should be available by end of August.FOR UPDATE and FOR NO KEY UPDATE: This will most likely be 1-2 months after that.Let me know if you have any feedback about the timeline and/or any use cases that are dependent on this.
Thanks for the question @incubus8!
SELECT FORhas a dependency on [#1199][YSQL] Support locking options in SELECT statement (SELECT FOR UPDATE etc.)@m-iancu or @ndeodhar would be the best folks to answer if there are any additional dependencies on top of the one above.
Thank you, you guys built amazing products!
Glad you like it 馃檹
Sorry for double posting, I was searching the issue but I couldn't find it.
Hi @incubus8, glad to hear that you like YugaByte DB!
We're going to start working on locking options forSELECTsoon and plan to do it in two phases:
- Support
FOR SHAREandFOR KEY SHARE: This should be available by end of August.- Support
FOR UPDATEandFOR NO KEY UPDATE: This will most likely be 1-2 months after that.Let me know if you have any feedback about the timeline and/or any use cases that are dependent on this.
Thank you so much @rkarthik007 @ndeodhar
The use case will be on most of database migration tools, in which most of Java app use it..
I believe most of this is done and now available in YugabyteDB, here is the GitHub issue that ended up tracking this: https://github.com/yugabyte/yugabyte-db/issues/1199
The docs are not yet updated. That is being tracked here: https://github.com/yugabyte/yugabyte-db/issues/2987
@jj-kim - could you please add any comments if needed and close the issue? Thanks!
Besides docs, this is done. Additional details are in #1199.
Most helpful comment
Sorry for double posting, I was searching the issue but I couldn't find it.
Thank you so much @rkarthik007 @ndeodhar
The use case will be on most of database migration tools, in which most of Java app use it..
For example:
https://github.com/flyway/flyway/blob/eb14b2d84f37a7396e30fbc4da285959ea50512c/flyway-core/src/main/java/org/flywaydb/core/internal/dbsupport/postgresql/PostgreSQLTable.java#L60