But why? SQL is supposed to be declarative, the whole point is that you don't need to care about such trivia. Only when you care about the order in a _result_ do you specify so.
How many times did that point have to be reiterated in unnecessary AI style?
Was the article AI generated. I hope so, if not it really shows how bad AI has degraded our ability to write. Could you at least have read over and cleaned up the prose a bit? That whole section could have been written in straight forward human language, and it would be shorter, clearer and less infuriating to read.
I research the topic, lay the outlines and let AI write it. Then I further refine section by section with a combination of AI and manual editing).
What you have pointed out is valid and it helps me to improve the process. And I have edited the post based on your suggestion.
As a non-native speaker and engineer with 15+ database development experience, I think I will continue to use AI to assist writing (I rarely use AI if I write in my native language). This post still takes me almost an afternoon to finish, but without AI, it will take me much more time.
Why do you think people will bother reading something you didn't bothered to write?
What I would argue is knowing what topic to write is more important, and I am confident if you throw this particular question to AI, the response would be much worse.
You can even graphically drag-and-drop column order from within SSMS (SQL Server Management Studio), although it’s always seemed sketch AF to me, and I wouldn’t want to do this with a large table unless I had backups and the site/app was set offline due to maintenance.
Even Entity Framework (DotNet) has the ability to define column order, but only on table create (for sure). I cannot remember if an EF migration can insert a column anywhere into the middle or not.