Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1.9.0 (and also 1.8.0) - the result of some generated SQL queries is not portable #54

Open
neilyoung opened this issue Feb 28, 2024 · 0 comments

Comments

@neilyoung
Copy link

...at least not from MySQL to MS SQL Server.

I'm not talking about this monster statement here, which I could only convert to MSSQL by use of ChatGPT (thanks, btw):

But also here: "LIMIT 1" might work in MySQL, but doesn't work in MSSQL.

Found at various places. Some constructs look like "overkill security", like suspenders AND belt, because their formulation cannot bring more than max result record at a time. Please review your tables to find another way to ensure uniqueness. One way would be to capture all candidates and then deliver just the last (if) by code.

Here the candidates:

public Optional<FlightAreaFileDTO> getLatestByWorkspaceId(String workspaceId) {

public Optional<GetMapElementsResponse> getCustomGroupByWorkspaceId(String workspaceId) {

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant