Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
smallint out of range error for exit codes on windows #657
Comments
|
@bcipriano I would like to take this issue up. |
|
Sounds good, I've assigned it to you! OpenCue uses database migrations to manage its database schema; Flyway has a good doc explaining this: https://flywaydb.org/getstarted/why Basically you will want to create a new migration file which makes the schema change. PR #618 is a good example to work from. Setting Up the Database | Apply Migrations from Source shows how this works in practice; once you have a migration, run There may be Cuebot changes needed to support the new datatype; again #618 is a good example of the Cuebot changes that were needed in that particular instance. |

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

I am getting the following error on windows:
Windows allows unsigned 32Bit exit codes which are larger than the
smallinttype ofint_exit_status.We could change the type of
int_exit_statustoINTEGERbut since postgres only has signed integers this would mean that we could still only represent half of the exit codes.The other option would be
BIGINTbut thats 8bytes which would be a lot of storage.https://docs.microsoft.com/en-gb/windows/win32/api/processthreadsapi/nf-processthreadsapi-exitprocess?redirectedfrom=MSDN
https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-dtyp/52ddd4c3-55b9-4e03-8287-5392aac0627f
The text was updated successfully, but these errors were encountered: