{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":11765017,"defaultBranch":"main","name":"Exposed","ownerLogin":"JetBrains","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2013-07-30T12:55:27.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/878437?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1725610857.0","currentOid":""},"activityList":{"items":[{"before":"6a47e0398da08d8c2398847b83b3578b36c40297","after":null,"ref":"refs/heads/joc/exposed-498","pushedAt":"2024-09-06T08:20:57.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"joc-a","name":"Jocelyne","path":"/joc-a","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/38375996?s=80&v=4"}},{"before":"61b1ebb81ec83369fe98697474dcaff2d9f21124","after":"bd74c5d41d3588c011971492df7f605f3760c1f6","ref":"refs/heads/main","pushedAt":"2024-09-06T08:20:54.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"joc-a","name":"Jocelyne","path":"/joc-a","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/38375996?s=80&v=4"},"commit":{"message":"feat: EXPOSED-498 Handle auto-increment status change on a column (#2216)\n\nThe function `MigrationUtils.statementsRequiredForDatabaseMigration` now includes the proper statements to change the type of a column when it detects that the auto-increment status has changed for PostgreSQL and SQL Server, and statements to create/drop the necessary sequences.\r\n\r\n- **Why**:\r\n\r\n**PostgreSQL**: The generated ALTER COLUMN statement was setting SERIAL as the target column type and that was throwing an error because it is not recognised as a type.\r\n\r\n**SQL Server**: The generated ALTER COLUMN statement was setting IDENTITY as the target column type and that was throwing an error because it is not possible to add it to an existing column later on and must be defined that way from the start.\r\n\r\n- **How**:\r\n\r\nTwo functions, `checkMissingSequences` and `checkUnmappedSequences` were added to `MigrationUtils`. For `checkUnmappedSequences`, H2_V1 is excluded because its system sequences do not have predictable naming patterns and it’s impossible to know if an existing sequence in the database is mapped in the Exposed code, so we would get false DROP statements that should not be there.\r\n\r\n**PostgreSQL**: The SQL equivalent to setting a column type as SERIAL was used. Check PostgreSQL documentation [here](https://www.postgresql.org/docs/current/datatype-numeric.html#DATATYPE-SERIAL). This means that when changing a column to be auto-incrementing in PostgreSQL, Exposed will generate three SQL statements:\r\n1. One to create a sequence\r\n2. One to set the column's default values to be assigned from a sequence generator\r\n3. One to set the column as the owner of the sequence created in Step 1\r\n\r\n**SQL Server**:\r\nThe simplest way to solve it is to create a new IDENTITY column and drop the old one. This means that when changing a column to be auto-incrementing in SQL Server, Exposed will generate three SQL statements:\r\n1. One to add a new IDENTITY column named \"NEW_columnName\"\r\n2. One to drop the old column\r\n3. One to rename the new column to the same name as the old dropped column","shortMessageHtmlLink":"feat: EXPOSED-498 Handle auto-increment status change on a column (<a class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"2489007866\" data-permission-text=\"Title is private\" data-url=\"https://github.com/JetBrains/Exposed/issues/2216\" data-hovercard-type=\"pull_request\" data-hovercard-url=\"/JetBrains/Exposed/pull/2216/hovercard\" href=\"https://github.com/JetBrains/Exposed/pull/2216\">#2216</a>"}},{"before":"61b1ebb81ec83369fe98697474dcaff2d9f21124","after":"5605f6ebfd7bb8646b9c920b491b98be0514c957","ref":"refs/heads/bog-walk/r2dbc-support","pushedAt":"2024-09-06T04:53:46.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"bog-walk","name":null,"path":"/bog-walk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/82039410?s=80&v=4"},"commit":{"message":"Organize initial structure of exposed-r2dbc module\n\n- Implement all API interfaces and abstract classes\n- Extract base logic from Database to new DatabaseApi and implement r2dbc versi>\n- Add dialect-specific metadata providers and example tests (Oracle and SQl Ser>\nare mostly not implemented)\n- Implement custom transaction manager, but need to decide on what to do with\ntransaction (existing blocks).","shortMessageHtmlLink":"Organize initial structure of exposed-r2dbc module"}},{"before":null,"after":"61b1ebb81ec83369fe98697474dcaff2d9f21124","ref":"refs/heads/bog-walk/r2dbc-support","pushedAt":"2024-09-05T19:59:16.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"bog-walk","name":null,"path":"/bog-walk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/82039410?s=80&v=4"},"commit":{"message":"docs: EXPOSED-515 How to identify composite key columns that use reference() (#2225)\n\n* docs: EXPOSED-515 How to identify composite key columns that use reference()\r\n\r\nThe documentation mentions that component columns of a composite key in\r\n`CompositeIdTable` should be marked using `entityId()`. If this is done on columns\r\nthat are already `Column<EntityID<?>>`, it will lead to another nested wrap. This\r\ncan be avoided by marking the component column using `addIdColumn()` in the table\r\ndefinition. An example of this using key columns that reference another table\r\nhas been included in both topics that explain how to define a `CompositeIdTable`.","shortMessageHtmlLink":"docs: EXPOSED-515 How to identify composite key columns that use refe…"}},{"before":"c167ce1ec3f2caf6bc64b7fdc02b725d54fa0b89","after":"0d67e47a51dcf59103f147c62c5a3ad56ddafacc","ref":"refs/heads/bog-walk/separate-offset-from-limit","pushedAt":"2024-09-05T16:11:32.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"bog-walk","name":null,"path":"/bog-walk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/82039410?s=80&v=4"},"commit":{"message":"feat!: EXPOSED-497 Allow OFFSET without LIMIT in query\n\n- Add default values to new interface members so implementations don't break\n- Remove default argument from old limit() to not conflict with new limit()\n- Update breaking changes document","shortMessageHtmlLink":"feat!: EXPOSED-497 Allow OFFSET without LIMIT in query"}},{"before":"eb6a4839d741e014ebc4e560df040b3fc254f972","after":"6a47e0398da08d8c2398847b83b3578b36c40297","ref":"refs/heads/joc/exposed-498","pushedAt":"2024-09-05T16:09:40.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"joc-a","name":"Jocelyne","path":"/joc-a","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/38375996?s=80&v=4"},"commit":{"message":"chore: Extract CREATE SEQUENCE and DROP SEQUENCE expected statements into functions","shortMessageHtmlLink":"chore: Extract CREATE SEQUENCE and DROP SEQUENCE expected statements …"}},{"before":"9f59756df551fea157b98a562294522a8dff4b93","after":"eb6a4839d741e014ebc4e560df040b3fc254f972","ref":"refs/heads/joc/exposed-498","pushedAt":"2024-09-05T16:09:21.000Z","pushType":"push","commitsCount":5,"pusher":{"login":"joc-a","name":"Jocelyne","path":"/joc-a","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/38375996?s=80&v=4"},"commit":{"message":"chore: Extract CREATE SEQUENCE and DROP SEQUENCE expected statements into functions","shortMessageHtmlLink":"chore: Extract CREATE SEQUENCE and DROP SEQUENCE expected statements …"}},{"before":"3b58b97b9170e7e40f8457a366afa7d45b8179d8","after":null,"ref":"refs/heads/bog-walk/add-composite-id-docs","pushedAt":"2024-09-03T21:46:09.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"bog-walk","name":null,"path":"/bog-walk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/82039410?s=80&v=4"}},{"before":"f7f57f166528946ffb0a43905347d5128f4d259c","after":"61b1ebb81ec83369fe98697474dcaff2d9f21124","ref":"refs/heads/main","pushedAt":"2024-09-03T21:45:09.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"bog-walk","name":null,"path":"/bog-walk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/82039410?s=80&v=4"},"commit":{"message":"docs: EXPOSED-515 How to identify composite key columns that use reference() (#2225)\n\n* docs: EXPOSED-515 How to identify composite key columns that use reference()\r\n\r\nThe documentation mentions that component columns of a composite key in\r\n`CompositeIdTable` should be marked using `entityId()`. If this is done on columns\r\nthat are already `Column<EntityID<?>>`, it will lead to another nested wrap. This\r\ncan be avoided by marking the component column using `addIdColumn()` in the table\r\ndefinition. An example of this using key columns that reference another table\r\nhas been included in both topics that explain how to define a `CompositeIdTable`.","shortMessageHtmlLink":"docs: EXPOSED-515 How to identify composite key columns that use refe…"}},{"before":"179427c07d3e27dac9a49d88673adafb37b5f370","after":null,"ref":"refs/heads/bog-walk/fix-column-isentityidentifier","pushedAt":"2024-09-03T20:58:35.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"bog-walk","name":null,"path":"/bog-walk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/82039410?s=80&v=4"}},{"before":"a6c676da3d5a47c4c472ebd2eaa04214ae337ce0","after":"f7f57f166528946ffb0a43905347d5128f4d259c","ref":"refs/heads/main","pushedAt":"2024-09-03T20:57:36.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"bog-walk","name":null,"path":"/bog-walk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/82039410?s=80&v=4"},"commit":{"message":"fix: EXPOSED-496 reference() idColumn equality check with referree's id is insufficient (#2222)\n\nisEntityIdentifier() relies currently on a column type to check whether that expression\r\nis the id column of an idTable. This fails if the column being checked is a reference\r\nentity id column to a referree table column that has the identical name. This happens\r\nbecause column equality is solely based on table and name.\r\n\r\nThe function now relies on a column, so that it's originating table can be taken\r\nmore into account, thereby ensuring no false positives.","shortMessageHtmlLink":"fix: EXPOSED-496 reference() idColumn equality check with referree's …"}},{"before":"c9a7afc5fb671d7e881d1988bd9c8f81887e2f53","after":"3b58b97b9170e7e40f8457a366afa7d45b8179d8","ref":"refs/heads/bog-walk/add-composite-id-docs","pushedAt":"2024-09-03T20:39:24.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"bog-walk","name":null,"path":"/bog-walk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/82039410?s=80&v=4"},"commit":{"message":"docs: EXPOSED-515 How to identify composite key columns that use reference()\n\nReduce duplicate content by using <include/>","shortMessageHtmlLink":"docs: EXPOSED-515 How to identify composite key columns that use refe…"}},{"before":"d6345da74f192e47101dde8bcd6e7e1c7f230a6e","after":null,"ref":"refs/heads/bog-walk/add-delete-from-join","pushedAt":"2024-09-03T20:20:25.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"bog-walk","name":null,"path":"/bog-walk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/82039410?s=80&v=4"}},{"before":"fe81af2da12f1462154ed5802db3b847caa1d34b","after":"a6c676da3d5a47c4c472ebd2eaa04214ae337ce0","ref":"refs/heads/main","pushedAt":"2024-09-03T20:18:03.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"bog-walk","name":null,"path":"/bog-walk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/82039410?s=80&v=4"},"commit":{"message":"feat!: EXPOSED-514 Support DELETE from tables in join (#2223)\n\n* feat!: EXPOSED-514 Support DELETE from tables in join\r\n\r\nUPDATE of a table from a join relation is already supported.\r\n\r\nThis adds the same functionality, but for DELETE. Rather than providing the values\r\nto update, the specific target table to delete rows from must be specified.\r\n\r\nRather than create a new class, DeleteStatement has been refactored to take a\r\nColumnSet that could either be a Table or a Join (like UpdateStatement). So the\r\ntable property and old constructor have been deprecated in favor of a new property\r\ntargetsSet and a constructor with the new property and a targetTables property.","shortMessageHtmlLink":"feat!: EXPOSED-514 Support DELETE from tables in join (<a class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"2499698275\" data-permission-text=\"Title is private\" data-url=\"https://github.com/JetBrains/Exposed/issues/2223\" data-hovercard-type=\"pull_request\" data-hovercard-url=\"/JetBrains/Exposed/pull/2223/hovercard\" href=\"https://github.com/JetBrains/Exposed/pull/2223\">#2223</a>)"}},{"before":"65509d9bc99d9815623764096cf8485554adaa1d","after":null,"ref":"refs/heads/documentation-website","pushedAt":"2024-09-02T08:31:47.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"joc-a","name":"Jocelyne","path":"/joc-a","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/38375996?s=80&v=4"}},{"before":"dc6942418038d11c49415a81956d5b672dc13d1f","after":"fe81af2da12f1462154ed5802db3b847caa1d34b","ref":"refs/heads/main","pushedAt":"2024-09-02T08:31:43.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"joc-a","name":"Jocelyne","path":"/joc-a","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/38375996?s=80&v=4"},"commit":{"message":"Update documentation website (#2221)\n\nCo-authored-by: joc-a <38375996+joc-a@users.noreply.github.com>","shortMessageHtmlLink":"Update documentation website (<a class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"2497177906\" data-permission-text=\"Title is private\" data-url=\"https://github.com/JetBrains/Exposed/issues/2221\" data-hovercard-type=\"pull_request\" data-hovercard-url=\"/JetBrains/Exposed/pull/2221/hovercard\" href=\"https://github.com/JetBrains/Exposed/pull/2221\">#2221</a>)"}},{"before":"a60700f1408152a0f443b16d4262ef232ff97cff","after":"9f59756df551fea157b98a562294522a8dff4b93","ref":"refs/heads/joc/exposed-498","pushedAt":"2024-09-02T08:29:41.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"joc-a","name":"Jocelyne","path":"/joc-a","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/38375996?s=80&v=4"},"commit":{"message":"feat: EXPOSED-498 Detect auto-increment status change on a column","shortMessageHtmlLink":"feat: EXPOSED-498 Detect auto-increment status change on a column"}},{"before":"2309299206a61ed8107a2de9ee57040965d74787","after":null,"ref":"refs/heads/exposed-513-drop-sequence-fails","pushedAt":"2024-09-02T08:28:29.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"joc-a","name":"Jocelyne","path":"/joc-a","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/38375996?s=80&v=4"}},{"before":"6c47d7aec17988d99860abca54ad3751a6374c08","after":"dc6942418038d11c49415a81956d5b672dc13d1f","ref":"refs/heads/main","pushedAt":"2024-09-02T08:28:25.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"joc-a","name":"Jocelyne","path":"/joc-a","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/38375996?s=80&v=4"},"commit":{"message":"fix: EXPOSED-513 DROP SEQUENCE fails when there is a dot in the sequence name (#2220)\n\nWhen attempting to drop all available sequences in Oracle and H2 Oracle, DROP SEQUENCE fails when there is a dot in the sequence name because the name obtained from the database is not quoted. The error thrown for Oracle states that the sequence is not found in the database. The error thrown for H2 Oracle states that the schema is not found in the database.\r\nIn the overridden `sequences()` function in `OracleDialect` and `H2Dialect`, there is now a check to see if the sequence name has a dot, and if it does and it's not already quoted, quotes are added. This way, when the sequence's `identifier` is used to drop it in the sequence's drop statement, it would succeed in finding and dropping the sequence.","shortMessageHtmlLink":"fix: EXPOSED-513 DROP SEQUENCE fails when there is a dot in the seque…"}},{"before":"6c47d7aec17988d99860abca54ad3751a6374c08","after":"c9a7afc5fb671d7e881d1988bd9c8f81887e2f53","ref":"refs/heads/bog-walk/add-composite-id-docs","pushedAt":"2024-09-02T00:28:25.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"bog-walk","name":null,"path":"/bog-walk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/82039410?s=80&v=4"},"commit":{"message":"docs: EXPOSED-515 How to identify composite key columns that use reference()\n\nThe documentation mentions that component columns of a composite key in\n`CompositeIdTable` should be marked using `entityId()`. If this is done on columns\nthat are already `Column<EntityID<?>>`, it will lead to another nested wrap. This\ncan be avoided by marking the component column using `addIdColumn()` in the table\ndefinition. An example of this using key columns that reference another table\nhas been included in both topics that explain how to define a `CompositeIdTable`.","shortMessageHtmlLink":"docs: EXPOSED-515 How to identify composite key columns that use refe…"}},{"before":null,"after":"6c47d7aec17988d99860abca54ad3751a6374c08","ref":"refs/heads/bog-walk/add-composite-id-docs","pushedAt":"2024-09-01T23:11:58.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"bog-walk","name":null,"path":"/bog-walk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/82039410?s=80&v=4"},"commit":{"message":"chore: Bump Exposed version from 0.53.0 to 0.54.0 (#2218)","shortMessageHtmlLink":"chore: Bump Exposed version from 0.53.0 to 0.54.0 (<a class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"2494728410\" data-permission-text=\"Title is private\" data-url=\"https://github.com/JetBrains/Exposed/issues/2218\" data-hovercard-type=\"pull_request\" data-hovercard-url=\"/JetBrains/Exposed/pull/2218/hovercard\" href=\"https://github.com/JetBrains/Exposed/pull/2218\">#2218</a>)"}},{"before":"a1ffd6fd64fccccaac723318bac75625a92f31bb","after":"efc32186d71f4885d3277ddf29e0007a47c0eaab","ref":"refs/heads/bog-walk/fix-multiline-string-upsert","pushedAt":"2024-09-01T20:45:27.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"bog-walk","name":null,"path":"/bog-walk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/82039410?s=80&v=4"},"commit":{"message":"fix: EXPOSED-509 Upsert with escaped multiline string fails in prepared statement\n\n- Remove accidentally left in println()","shortMessageHtmlLink":"fix: EXPOSED-509 Upsert with escaped multiline string fails in prepar…"}},{"before":"46130c5189d2ec57b3fa0113eb9f5ef5b49d6c7b","after":"d6345da74f192e47101dde8bcd6e7e1c7f230a6e","ref":"refs/heads/bog-walk/add-delete-from-join","pushedAt":"2024-09-01T20:40:06.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"bog-walk","name":null,"path":"/bog-walk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/82039410?s=80&v=4"},"commit":{"message":"feat!: EXPOSED-514 Support DELETE from tables in join\n\n- Fix detekt issue & docs","shortMessageHtmlLink":"feat!: EXPOSED-514 Support DELETE from tables in join"}},{"before":"6c47d7aec17988d99860abca54ad3751a6374c08","after":"46130c5189d2ec57b3fa0113eb9f5ef5b49d6c7b","ref":"refs/heads/bog-walk/add-delete-from-join","pushedAt":"2024-09-01T03:35:26.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"bog-walk","name":null,"path":"/bog-walk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/82039410?s=80&v=4"},"commit":{"message":"feat!: EXPOSED-514 Support DELETE from tables in join\n\nUPDATE of a table from a join relation is already supported.\n\nThis adds the same functionality, but for DELETE. Rather than providing the values\nto update, the specific target table to delete rows from must be specified.\n\nRather than create a new class, DeleteStatement has been refactored to take a\nColumnSet that could either be a Table or a Join (like UpdateStatement). So the\ntable property and old constructor have been deprecated in favor of a new property\ntargetsSet and a constructor with the new property and a targetTables property.","shortMessageHtmlLink":"feat!: EXPOSED-514 Support DELETE from tables in join"}},{"before":"6c47d7aec17988d99860abca54ad3751a6374c08","after":"c167ce1ec3f2caf6bc64b7fdc02b725d54fa0b89","ref":"refs/heads/bog-walk/separate-offset-from-limit","pushedAt":"2024-08-31T16:35:31.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"bog-walk","name":null,"path":"/bog-walk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/82039410?s=80&v=4"},"commit":{"message":"feat!: EXPOSED-497 Allow OFFSET without LIMIT in query\n\nAll dialects except SQLite and MySQL/MariaDB allow OFFSET clause to be used at the\nend of a query without an associated LIMIT clause. This is currently not possible\nto accomplish without creating a custom query or providing a very large number,\nas a limit must be provided to get an offset.\n\nThis splits SizedIterable.limit() into 2 respective functions, introducing a breaking\nchange for the interface. It also creates a new FunctionProvider.queryLimitAndOffset()\nto replace the original, so that a nullable limit can be passed.","shortMessageHtmlLink":"feat!: EXPOSED-497 Allow OFFSET without LIMIT in query"}},{"before":"6c47d7aec17988d99860abca54ad3751a6374c08","after":"179427c07d3e27dac9a49d88673adafb37b5f370","ref":"refs/heads/bog-walk/fix-column-isentityidentifier","pushedAt":"2024-08-31T03:24:43.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"bog-walk","name":null,"path":"/bog-walk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/82039410?s=80&v=4"},"commit":{"message":"fix: EXPOSED-496 reference() idColumn equality check with referree's id is insufficient\n\nisEntityIdentifier() relies currently on a column type to check whether that expression\nis the id column of an idTable. This fails if the column being checked is a reference\nentity id column to a referree table column that has the identical name. This happens\nbecause column equality is solely based on table and name.\n\nThe function now relies on a column, so that it's originating table can be taken\nmore into account, thereby ensuring no false positives.","shortMessageHtmlLink":"fix: EXPOSED-496 reference() idColumn equality check with referree's …"}},{"before":"6c47d7aec17988d99860abca54ad3751a6374c08","after":"a1ffd6fd64fccccaac723318bac75625a92f31bb","ref":"refs/heads/bog-walk/fix-multiline-string-upsert","pushedAt":"2024-08-31T02:40:57.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"bog-walk","name":null,"path":"/bog-walk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/82039410?s=80&v=4"},"commit":{"message":"fix: EXPOSED-509 Upsert with escaped multiline string fails in prepared stateme>\n\nThe update clause of an upsert statement is being prepared without appropriate\nparameterisation, leading to any multiline strings being treated as string lite>\nand escaped, thereby losing any indentation.\n\nThis occurs because the appropriate registerArgument() invokations are not being used,\nparticularly for databases that use merge syntax.","shortMessageHtmlLink":"fix: EXPOSED-509 Upsert with escaped multiline string fails in prepar…"}},{"before":null,"after":"6c47d7aec17988d99860abca54ad3751a6374c08","ref":"refs/heads/bog-walk/fix-column-isentityidentifier","pushedAt":"2024-08-31T02:18:06.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"bog-walk","name":null,"path":"/bog-walk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/82039410?s=80&v=4"},"commit":{"message":"chore: Bump Exposed version from 0.53.0 to 0.54.0 (#2218)","shortMessageHtmlLink":"chore: Bump Exposed version from 0.53.0 to 0.54.0 (<a class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"2494728410\" data-permission-text=\"Title is private\" data-url=\"https://github.com/JetBrains/Exposed/issues/2218\" data-hovercard-type=\"pull_request\" data-hovercard-url=\"/JetBrains/Exposed/pull/2218/hovercard\" href=\"https://github.com/JetBrains/Exposed/pull/2218\">#2218</a>)"}},{"before":null,"after":"6c47d7aec17988d99860abca54ad3751a6374c08","ref":"refs/heads/bog-walk/fix-multiline-string-upsert","pushedAt":"2024-08-30T16:13:37.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"bog-walk","name":null,"path":"/bog-walk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/82039410?s=80&v=4"},"commit":{"message":"chore: Bump Exposed version from 0.53.0 to 0.54.0 (#2218)","shortMessageHtmlLink":"chore: Bump Exposed version from 0.53.0 to 0.54.0 (<a class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"2494728410\" data-permission-text=\"Title is private\" data-url=\"https://github.com/JetBrains/Exposed/issues/2218\" data-hovercard-type=\"pull_request\" data-hovercard-url=\"/JetBrains/Exposed/pull/2218/hovercard\" href=\"https://github.com/JetBrains/Exposed/pull/2218\">#2218</a>)"}},{"before":null,"after":"6c47d7aec17988d99860abca54ad3751a6374c08","ref":"refs/heads/bog-walk/separate-offset-from-limit","pushedAt":"2024-08-30T16:11:25.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"bog-walk","name":null,"path":"/bog-walk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/82039410?s=80&v=4"},"commit":{"message":"chore: Bump Exposed version from 0.53.0 to 0.54.0 (#2218)","shortMessageHtmlLink":"chore: Bump Exposed version from 0.53.0 to 0.54.0 (<a class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"2494728410\" data-permission-text=\"Title is private\" data-url=\"https://github.com/JetBrains/Exposed/issues/2218\" data-hovercard-type=\"pull_request\" data-hovercard-url=\"/JetBrains/Exposed/pull/2218/hovercard\" href=\"https://github.com/JetBrains/Exposed/pull/2218\">#2218</a>)"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAErq7cMAA","startCursor":null,"endCursor":null}},"title":"Activity · JetBrains/Exposed"}