Skip to content

Tags: specify/specify7

Tags

v7.11.3

Toggle v7.11.3's commit message
fix customized formatters

v7.11.2.1

Toggle v7.11.2.1's commit message
Refactor picklist handling to improve null handling and type coercion…

… when building a case statement for the QB.

v7.11.2

Toggle v7.11.2's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore(changelog): add 7.11.2 release notes

v7.11.1

Toggle v7.11.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Update CHANGELOG.md

v7.11.0.2

Toggle v7.11.0.2's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Add changelog update

v7.11.0.1

Toggle v7.11.0.1's commit message
Resolve business rule

v7.11.0

Toggle v7.11.0's commit message
Support whitespaces between Django security variables

v7.10.2.3

Toggle v7.10.2.3's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Merge pull request #6502 from specify/issue-6488

Don't trigger unload protect when re-opening to-one resource in dialog

v7.10.2.2

Toggle v7.10.2.2's commit message
Simplify find_tree_and_field

v7.10.2.1

Toggle v7.10.2.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Hotfixes: Fullname query hotfix + catalog number cast hotfix for `7.1…

…0.2` (#6465)

* Handle case where rank name has spaces

* Use name as default tree rank query

* Handle edge case for fullname query

* Use name for fullname

* Skip test temporarily

* Revert mapping for fullname

* Fix case for fullName query with 1 space in rank
- Also adds a unit test to ensure this doesn't break again

* Cast catalogNumber to Numeric in query results if all formats are numeric

Fixes #6464
See related #5485 and #6245

This handles the most common case.
In the case where there exists both numeric and non-numeric formats for
catalogNumber, the numeric formats will still be cast as a string.
This also ONLY works with formats called CatalogNumberNumeric;
i.e., any other purely numeric format will not be considered as numeric
by the QueryBuilder

* Add comment to catalogNumber cast for queries

---------

Co-authored-by: melton-jason <meltonjason12@yahoo.com>