You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* chore: add grpc-server API for SpannerLib
Adds a gRPC server that exposes the API of SpannerLib. This allows clients
to connect to run SpannerLib as a child process and connect to it using
gRPC.
* refactor(ruby): Introduce MessageHandler and Rows classes (#553)
* refactor: add new message handler in ruby wrapper
* chore: delay transaction activation until actual use (#552)
* chore: store temp TransactionOptions in connection state
Store temporary TransactionOptions in the connection state as local options. Local options
only apply to the current transaction. This simplifies the internal state handling of the
driver, as all transaction state should only be read from the connection state, and not
also from a temporary variable.
This also enables the use of a combination of temporary transaction options and using
SQL statements to set further options. The shared library always includes temporary
transaction options, as the BeginTransaction function accepts TransactionOptions as an
input argument. This meant that using SQL statements to set further transaction options
was not supported through the shared library.
* chore: delay transaction activation until actual use
Delay the actual transaction activation until the first actual usage of the transaction.
That is; the first time that a statement is being sent to Spanner. This allows the
application to amend the transaction options after calling BeginTx or executing
`BEGIN TRANSACTION`. The transaction options can be amended by executing a statement
like `SET TRANSACTION READ ONLY`.
* chore: update actions/checkout action to v5 (#555)
* fix: update all dependencies (#551)
* fix: update all dependencies
* chore: go mod tidy
---------
Co-authored-by: Knut Olav Løite <koloite@gmail.com>
* chore: add signal handler to remove temp file
* chore: add .NET gRPC wrapper (#539)
* fix: update dependency net.java.dev.jna:jna to v5.18.0 (#538)
* chore: update all dependencies (#537)
* fix: update all dependencies (#536)
* fix: update all dependencies
* chore: go mod tidy
---------
Co-authored-by: Knut Olav Løite <koloite@gmail.com>
* chore(main): release 1.18.1 (#525)
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
* fix: update module github.com/googleapis/go-sql-spanner to v1.18.1 (#540)
* chore: add .NET gRPC wrapper
Adds a gRPC wrapper for .NET. This wrapper uses the gRPC API to connect to SpannerLib.
The gRPC channel uses a Unix domain socket.
* fix: update dependency net.java.dev.jna:jna to v5.18.1 (#544)
This PR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| [net.java.dev.jna:jna](https://redirect.github.com/java-native-access/jna) | `5.18.0` -> `5.18.1` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) |
---
### Release Notes
<details>
<summary>java-native-access/jna (net.java.dev.jna:jna)</summary>
### [`v5.18.1`](https://redirect.github.com/java-native-access/jna/blob/HEAD/CHANGES.md#Release-5181)
[Compare Source](https://redirect.github.com/java-native-access/jna/compare/5.18.0...5.18.1)
\==============
## Bug Fixes
- [#​1686](https://redirect.github.com/java-native-access/jna/issues/1686): Fix `sortFields` race condition while getting fields - [@​bendk](https://redirect.github.com/bendk).
</details>
---
### Configuration
📅 **Schedule**: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) (UTC), Automerge - At any time (no schedule defined).
🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.
♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 **Ignore**: Close this PR and you won't be reminded about this update again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box
---
This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/googleapis/go-sql-spanner).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xMzEuOSIsInVwZGF0ZWRJblZlciI6IjQxLjEzMS45IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
* feat: add authority param support to DSN (#546)
Signed-off-by: Marco Pracucci <marco@pracucci.com>
* fix: update all dependencies (#542)
* fix: update all dependencies
* chore: go mod tidy
* build: add ByteBuddy for Java wrapper
---------
Co-authored-by: Knut Olav Løite <koloite@gmail.com>
* feat(ruby): Add Ruby FFI wrapper for spannerlib (#545)
* feat(ruby): add Ruby FFI wrapper for spannerlib
* chore(main): release 1.19.0 (#541)
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
* chore: store temp TransactionOptions in connection state (#548)
Store temporary TransactionOptions in the connection state as local options. Local options
only apply to the current transaction. This simplifies the internal state handling of the
driver, as all transaction state should only be read from the connection state, and not
also from a temporary variable.
This also enables the use of a combination of temporary transaction options and using
SQL statements to set further options. The shared library always includes temporary
transaction options, as the BeginTransaction function accepts TransactionOptions as an
input argument. This meant that using SQL statements to set further transaction options
was not supported through the shared library.
* feat: parse SET TRANSACTION statements (#549)
* feat: parse SET TRANSACTION statements
Parse SET TRANSACTION statements and translate these to SET LOCAL statements.
SET TRANSACTION may only be executed in a transaction block, and can only be
used for a specific, limited set of connection properties. The syntax is
specified by the SQL standard and PostgreSQL.
See also https://www.postgresql.org/docs/current/sql-set-transaction.html
This change only adds partial support. The following features will be added
in future changes:
1. SET TRANSACTION READ {WRITE | ONLY} is not picked up by the driver, as
the type of transaction is set directly when BeginTx is called. A
refactor of this transaction handling is needed to be able to pick up
SET TRANSACTION READ ONLY / SET TRANSACTION READ WRITE statements that
are executed after BeginTx has been called.
2. PostgreSQL allows multiple transaction modes to be set in a single
SET TRANSACTION statement. E.g. the following is allowed:
SET TRANSACTION READ WRITE, ISOLATION LEVEL SERIALIZABLE
The current implementation only supports one transaction mode per
SET statement.
* feat: support multiple transaction options in one statement
* feat: support transaction options in BEGIN statements (#550)
* feat: parse SET TRANSACTION statements
Parse SET TRANSACTION statements and translate these to SET LOCAL statements.
SET TRANSACTION may only be executed in a transaction block, and can only be
used for a specific, limited set of connection properties. The syntax is
specified by the SQL standard and PostgreSQL.
See also https://www.postgresql.org/docs/current/sql-set-transaction.html
This change only adds partial support. The following features will be added
in future changes:
1. SET TRANSACTION READ {WRITE | ONLY} is not picked up by the driver, as
the type of transaction is set directly when BeginTx is called. A
refactor of this transaction handling is needed to be able to pick up
SET TRANSACTION READ ONLY / SET TRANSACTION READ WRITE statements that
are executed after BeginTx has been called.
2. PostgreSQL allows multiple transaction modes to be set in a single
SET TRANSACTION statement. E.g. the following is allowed:
SET TRANSACTION READ WRITE, ISOLATION LEVEL SERIALIZABLE
The current implementation only supports one transaction mode per
SET statement.
* feat: support multiple transaction options in one statement
* feat: support transaction options in BEGIN statements
Adds support for including transaction options in BEGIN statements, like:
```sql
BEGIN READ ONLY;
BEGIN READ WRITE;
BEGIN TRANSACTION ISOLATION LEVEL REPEATABLE READ;
BEGIN READ WRITE, ISOLATION LEVEL SERIALIZABLE;
```
* chore: re-trigger checks
* chore: add timeout for server startup
---------
Signed-off-by: Marco Pracucci <marco@pracucci.com>
Co-authored-by: Mend Renovate <bot@renovateapp.com>
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Co-authored-by: Marco Pracucci <marco@pracucci.com>
Co-authored-by: aakashanandg <aakashanand@google.com>
* chore: return long instead of int
* chore: remove TODO
---------
Signed-off-by: Marco Pracucci <marco@pracucci.com>
Co-authored-by: aakashanandg <aakashanand@google.com>
Co-authored-by: Mend Renovate <bot@renovateapp.com>
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Co-authored-by: Marco Pracucci <marco@pracucci.com>
t.Fatalf("error mismatch for starting a DML batch while in a read-only transaction\nGot: %v\nWant: %v", spanner.ErrCode(err), codes.FailedPrecondition)
108
108
}
109
109
110
110
// Starting a DML batch while the connection is in a read/write transaction is allowed.
0 commit comments