--Approach 1: The all in one WTF
-- Advantage: 1 step and no temp junk created
-- so safe to nest into other subqueries and reuse
--- Disadvantage: Messy to read,
-- could be slow for large sets,
-- and relies on a primary key
SELECT row_number, oldtable.*
FROM (SELECT * FROM people) As oldtable
CROSS JOIN (SELECT ARRAY(SELECT name_id
FROM people
ORDER BY last_name, first_name) As id) AS oldids
CROSS JOIN generate_series(1, (SELECT COUNT(*)
FROM people)) AS row_number
"I'm more wondering why the query optimizer would ever use the plan it currently does."
To put it another way, the question is why the following plan looks cheapest to the optimizer, compared with the alternatives (of which there are many).
The inner side of the join is essentially runnin...
So, how can I get such a unique id for a transaction in the transaction logs?
Stop trying to use the transaction log for these types of situations. Take any notion you have of using the log for data mining and defenestrate it.
Or should I use SQL server audit? Is there a way to query the...
