fix(postgres): avoid UNSIGNED cast in customer autoname #51558
+31
−6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fix Customer autoname on Postgres by removing MariaDB-only
CAST(... AS UNSIGNED).Problem
Creating a Customer (including via Sales Invoice customer field) can fail on Postgres with:
Root cause:
Customer.get_customer_name()usesCAST(... AS UNSIGNED)to compute the next suffix when a duplicate name exists.Fix
Customer - 3using:SUBSTRING(name FROM '\d+$')and cast toINTEGER.Tests
pre-commit run --all-files✅Test, thenTest - 1,Test - 2).Notes
Server-side logic only; no UI changes.