connect-by

Don't we hate when evil coding comes back to haunt? Some time ago I needed to generate a string concatenating some fields for some more processing later. I thought it would be a good idea to do if straight in the query, and used SO's help to get it. It worked. For a while... The table got to big and now that trick (which I know is super inefficient) is not exactly viable. This what I'm doing: with my_tabe as ( select 'user1' as usrid, '1' as prodcode from dual union select 'user1' as usrid, '2' as prodcode from dual union select 'user1' as usrid, '3' as prodcode from dual union select 'user2'

In Oracle , if I have a table defined as … CREATE TABLE taxonomy ( key NUMBER(11) NOT NULL CONSTRAINT taxPkey PRIMARY KEY, value VARCHAR2(255), taxHier NUMBER(11) ); ALTER TABLE taxonomy ADD CONSTRAINT taxTaxFkey FOREIGN KEY (taxHier) REFERENCES tax(key); With these values … key value taxHier 0 zero null 1 one 0 2 two 0 3 three 0 4 four 1 5 five 2 6 six 2 This query syntax … SELECT value FROM taxonomy CONNECT BY PRIOR key = taxHier START WITH key = 0; Will yield … zero one four two five six three How is this done in PostgreSQL ? Erwin Brandstetter Use a RECURSIVE CTE in Postgres: WITH

I've got this Oracle code structure I'm trying to convert to SQL Server 2008 ( Note: I have used generic names, enclosed column names and table names within square brackets '[]', and done some formatting to make the code more readable) : SELECT [col#1], [col#2], [col#3], ..., [col#n], [LEVEL] FROM (SELECT [col#1], [col#2], [col#3], ..., [col#n] FROM [TABLE_1] WHERE ... ) CONNECT BY PRIOR [col#1] = [col#2] START WITH [col#2] IS NULL ORDER SIBLINGS BY [col#3] What is the SQL Server equivalent template of the above code? Specifically, I'm struggling with the LEVEL , and 'ORDER SIBLINGS BY' Oracle