excessive query diffs after build #414
Replies: 1 comment
-
In my experience, the first time you build a database from source, you will typically see some "noise" when you export the new build. I usually just commit those changes as "Build from source". Subsequent builds of the same project should (ideally) not create any new changes in git. If you build from source, tweak a form, export, build from source again, the source file from the form should be the only thing showing as a change in the repository. That being said, queries can be a bit of an interesting component. If you edit the query in the SQL view, it is saved one way, whereas if you save it through the designer, it is saved another way. You also have factors like Access optimizing queries, and some rare issues with specific join scenarios. You can find some discussions on these in previous issues.
You also have an option to force the import of the SQL during build, which can help in some edge case scenarios. I would recommend reading through the issues mentioned above first, as those contain some helpful tips for understanding VCS changes in query objects. Hope that helps! |
Beta Was this translation helpful? Give feedback.
-
Hi,
Is there a known issue with excessive query diffs after build?
When I do this flow, I should expect no changes, correct?
Export > Commit > Build > Export
Instead, get the same 100+ queries every time after build.
It appears the discrepancy is in the
![image](https://private-user-images.githubusercontent.com/2698896/253361983-cb4a11b6-8ad4-4de7-946f-88e03c52d3b5.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTg2Nzg2NzksIm5iZiI6MTcxODY3ODM3OSwicGF0aCI6Ii8yNjk4ODk2LzI1MzM2MTk4My1jYjRhMTFiNi04YWQ0LTRkZTctOTQ2Zi04OGUwM2M1MmQzYjUucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDYxOCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA2MThUMDIzOTM5WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZGZmZDNmYTdjMzFmODViMGM2OWIzZjVmMjUyOWZhOWFiMzZkOGFmNjdkZjExNjMwYzZlNTI4ZWI4NmM3MDI2ZiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.Hpbq7RymqN9oAxZPek4hBDamm6MQBGnSDFqM5xlJ22U)
JOIN
clause reordering the join fields.I believe I've seen similar reordering of fields on the
WHERE
clause as well but can't find the example ATM.TIA
Beta Was this translation helpful? Give feedback.
All reactions