Updated oid and column_order fields to only allow positive integers

[varshadr]

Fixes #3176

This PR addresses constraints for the oid field and the column_order field in the TableSettings object. Both fields currently allow negative integers. This update ensures that oid and column_order only accepts positive integers.

Checklist

• My pull request has a descriptive title (not a vague title like Update index.md).
• My pull request targets the develop branch of the repository
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no
  visible errors.

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[silentninja]

@varshadr Please run makemigrations to generate the migration file for converting the existing database columns and add it to the PR.

[varshadr]

@varshadr Please run makemigrations to generate the migration file for converting the existing database columns and add it to the PR.

Okay 👍

[seancolsen]

@varshadr I'm re-assigning this to @mathemancer because Mukesh will no longer be working with you on this project. Please assign any further PRs to @mathemancer for review.

[varshadr]

@varshadr I'm re-assigning this to @mathemancer because Mukesh will no longer be working with you on this project. Please assign any further PRs to @mathemancer for review.

Sure 👍

[Anish9901]

This is looking great @varshadr! Can you add some tests to verify that the validator is working as intended?

[varshadr]

This is looking great @varshadr! Can you add some tests to verify that the validator is working as intended?

Hey @Anish9901
I have never written tests before, I'll give it a try though!

[seancolsen]

I put this in the v0.1.4 milestone because we'd like to Clean up django migrations before 0.1.4 release and this PR introduces migrations (so we want to merge it before we clean up the migrations).

[Anish9901]

@varshadr for the sake of merging this PR I am taking over writing the test cases, please let me know if you have any concerns.

[varshadr]

@varshadr for the sake of merging this PR I am taking over writing the test cases, please let me know if you have any concerns.

Sure, you could go on with it

Review addressed