Breaking Change: ID fields will become int64 #263
Assignees
Labels
Comments
apricote
added a commit
that referenced
this issue
Jul 5, 2023
The `int` datatype is not guaranteed to offer 64 bits of precision. On 32-bit platforms it only has 32 bits of precision. This is incompatible with the Hetzner Cloud identifiers having up to 52-bits after September 1st 2023. See #263 for more details about this change.
apricote
added a commit
that referenced
this issue
Jul 5, 2023
The `int` datatype is not guaranteed to offer 64 bits of precision. On 32-bit platforms it only has 32 bits of precision. This is incompatible with the Hetzner Cloud identifiers having up to 52-bits after September 1st 2023. See #263 for more details about this change.
apricote
added a commit
that referenced
this issue
Jul 5, 2023
The `int` datatype is not guaranteed to offer 64 bits of precision. On 32-bit platforms it only has 32 bits of precision. This is incompatible with the Hetzner Cloud identifiers having up to 52-bits after September 1st 2023. See #263 for more details about this change.
This was referenced Jul 5, 2023
apricote
added a commit
that referenced
this issue
Jul 6, 2023
The `int` datatype is not guaranteed to offer 64 bits of precision. On 32-bit platforms it only has 32 bits of precision. This is incompatible with the Hetzner Cloud identifiers having up to 52-bits after September 1st 2023. See #263 for more details about this change.
apricote
added a commit
that referenced
this issue
Jul 12, 2023
The `int` datatype is not guaranteed to offer 64 bits of precision. On 32-bit platforms it only has 32 bits of precision. This is incompatible with the Hetzner Cloud identifiers having up to 52-bits after September 1st 2023. See #263 for more details about this change.
|
Version Until then, we will keep backporting changes to 1.x and releasing new versions. |
This comment was marked as outdated.
This comment was marked as outdated.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
52-bit IDs
Our API documentation specified the type for all ID fields as
integer. We have realized that this was not sufficient and that some users of our API (like our ownhcloud-go) assumed that 32-bit integers would be enough. Soon we will have IDs with up to 52 bits, and this can cause issues if your code does not handle this properly. Please make sure that your integration with our API uses 64-bit integers (also calledlongin many languages) for all ID fields, and fields that contain IDs such asnetwork.servers.We will start using the larger IDs after September 1st 2023.
To comply with this, we plan on releasing a new major version of our own
hcloud-golibrary to switch the data type for IDs frominttoint64in the next weeks. We will maintain the existing version as well as the new version for the migration period.Important: To avoid any issue, you should make sure that all necessary changes are already completed by the time mentioned above.
The text was updated successfully, but these errors were encountered: