@bbaird Sorry to hear about your work situation, but definitely reassures me I wasn't crazy when I went through the same thing (fortunately the people I worked with were reasonable and listened to the facts).
My favorite part of exploring AWS to try to meet our business needs, was very simple business problems couldn't be solved over the course of 3 months between 5 meetings involving about 8 Solutions Architects from AWS. Like they were trying to sell us on technology their SAs had no clue on how to use. 🤐
It seems like you can't really win this. When you first write it, it's better to have the FROM on the top, but then when you are using it later, it's better to have the SELECT on the top. And since 90% of software's life is in maintenance, I guess that's probably the right choice.
SELECT in ISO/IEC-standard SQL prescribes the following syntactical order for the sub-clauses:
SELECT
projection-expressions
FROM
sources
WHERE
predicate-expression
GROUP BY
key-expression
HAVING
predicate-expression
ORDER BY
ordering-expressions
While the logical execu...
> It is always a struggle to explain, even though I understand the reasons perfectly well, that every appearance of a column reference in the SELECT clause of a grouped query must either be a reference to a grouping column or be inside an invocation of an aggregate operator such as SUM.
@J.D. I've decided the best course of action at this point is to give them the finger, spend time finishing our existing solution, then put the onus on them if they want to do anything other than host the SQL Server in a different environment.
Like "hey, this is working, whatever you do will have to do the same or better, and the development costs will have to be less than the cost savings from the different technology used."
Yea unfortunately some people's minds can't be changed to see anything other than what they want to see, usually the less technically inclined. Best of luck mate!
"As before for this correctly to work, you need an order. onöly ordering it by id_ isn't usually enough to get the job done, it would be terr whenyou can add another order to the hole thing"
As before for this correctly to work, you need an order. onöly ordering it by id_ isn't usually enough to get the job done, it would be terr whenyou can add another order to the hole thing
CREATE TABLE IF NOT EXISTS t1 (
id_ INTEGER NOT NULL,
value1 INT NOT NULL);
INSERT INTO t1 (id_, v...
SELECT in ISO/IEC-standard SQL prescribes the following syntactical order for the sub-clauses:
SELECT
projection-expressions
FROM
sources
WHERE
predicate-expression
GROUP BY
key-expression
HAVING
predicate-expression
ORDER BY
ordering-expressions
While the logical execu...
As before for this correctly to work, you need an order. onöly ordering it by id_ isn't usually enough to get the job done, it would be terr whenyou can add another order to the hole thing
CREATE TABLE IF NOT EXISTS t1 (
id_ INTEGER NOT NULL,
value1 INT NOT NULL);
INSERT INTO t1 (id_, v...
