From: | Igor Neyman <ineyman(at)perceptron(dot)com> |
---|---|
To: | Michael Moore <michaeljmoore(at)gmail(dot)com>, postgres list <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: simple function index question |
Date: | 2016-03-23 15:57:21 |
Message-ID: | A76B25F2823E954C9E45E32FA49D70ECCD68070C@mail.corp.perceptron.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
From: pgsql-sql-owner(at)postgresql(dot)org [mailto:pgsql-sql-owner(at)postgresql(dot)org] On Behalf Of Michael Moore
Sent: Wednesday, March 23, 2016 11:14 AM
To: postgres list <pgsql-sql(at)postgresql(dot)org>
Subject: Re: [SQL] simple function index question
Thanks guys,
I agree that the data model is suspect. I'm trying to convert from Oracle to Postgres and changing table structures is not really an option for me. I tried casting the null, ... same problem. It does not like the undefined record type as David is saying. I will try his solution and let you know how it goes.
Interestingly a version of this:
CREATE INDEX TX_QSET_DIR_MAP_PRI_URI_TYP_UK
ON tx_question_set_dir_map
USING btree
(question_set2tx_question_set ,uri_type,
(CASE WHEN uri_type = 201900 THEN null::varchar(100)
ELSE question_set_dir_map_key END);
Worked for me. Try it if you are still interested.
Just do proper casting of null (it was varchar(100) in my case).
Regards,
Igor Neyman
From | Date | Subject | |
---|---|---|---|
Next Message | Igor Neyman | 2016-03-23 16:10:01 | Re: simple function index question |
Previous Message | bricklen | 2016-03-23 15:34:03 | Re: simple function index question |