Currently, this we are running in production, not faced any issues with functional or performance or database maintenance, I am talking about banking related application
As per my knowledge/experience this should work without any downside,
and, this cast creation method is part of postgresql document from 8.4
Thanks
Sridhar BN
On Sun, Feb 22, 2015 at 7:39 AM, Ken Tanzer <ken.tanzer@xxxxxxxxx> wrote:
I tried that and it does indeed work. (With, of course, the appropriate permissions to create the cast.)So this makes me wonder--is there any downside or unwelcome side effects to having such a cast? And if not, why isn't it part of the default setup?Cheers,KenOn Sat, Feb 21, 2015 at 3:34 AM, sridhar bamandlapally <sridhar.bn1@xxxxxxxxx> wrote:HiPlease see below, this works, way for implicit type castingbns=# CREATE TEMP TABLE foo (my_array varchar[]);CREATE TABLEbns=#bns=# INSERT INTO foo (my_array) SELECT '{TEST}';INSERT 0 1bns=#bns=# SELECT my_array[1],array_length(my_array,1) FROM foo;my_array | array_length----------+--------------TEST | 1(1 row)bns=#bns=# INSERT INTO foo (my_array) SELECT DISTINCT '{TEST}';ERROR: column "my_array" is of type character varying[] but _expression_ is of type textLINE 1: INSERT INTO foo (my_array) SELECT DISTINCT '{TEST}';^HINT: You will need to rewrite or cast the _expression_.bns=#bns=# CREATE CAST (text AS varchar[]) WITH INOUT AS IMPLICIT;CREATE CASTbns=#bns=# INSERT INTO foo (my_array) SELECT DISTINCT '{TEST}'; ---- this worksINSERT 0 1bns=#bns=#in previous mail, sorry for not mentioning varchar"[]"We did type cast implicit method to avoid application code changes for Oracle to PostgreSQL compatibleThanksSridhar BNOn Sat, Feb 21, 2015 at 9:38 AM, Ken Tanzer <ken.tanzer@xxxxxxxxx> wrote:I'm not able to run this unless I'm the Postgres super user. But if I run it as such, it tells me that cast already exists anyway.CREATE CAST (text AS varchar) WITH INOUT AS IMPLICIT;ERROR: cast from type text to type character varying already existsOf course this will work fine:INSERT INTO foo (my_array) SELECT DISTINCT '{TEST}'::varchar[];I was mostly surprised by having DISTINCT added to a SELECT make things break. It may be too obscure an issue to be worth adding, but nothing on the DISTINCT documentation suggests this possibility."If DISTINCT is specified, all duplicate rows are removed from the result set..."Cheers,KenOn Fri, Feb 20, 2015 at 6:30 PM, sridhar bamandlapally <sridhar.bn1@xxxxxxxxx> wrote:>>>ERROR: column "my_array" is of type character varying[] but _expression_ is of type textplease try this below, may be this should helpCREATE CAST (text AS varchar) WITH INOUT AS IMPLICIT;just for info:actually this should be available in defaultOn Fri, Feb 20, 2015 at 9:48 AM, Ken Tanzer <ken.tanzer@xxxxxxxxx> wrote:Hi. Here's a boiled down example of something that caught me by surprise:ag_reach_test=> CREATE TEMP TABLE foo (my_array varchar[]);CREATE TABLEag_reach_test=> INSERT INTO foo (my_array) SELECT '{TEST}';INSERT 0 1ag_reach_test=> SELECT my_array[1],array_length(my_array,1) FROM foo;my_array | array_length----------+--------------TEST | 1(1 row)ag_reach_test=> INSERT INTO foo (my_array) SELECT DISTINCT '{TEST}';ERROR: column "my_array" is of type character varying[] but _expression_ is of type textLINE 1: INSERT INTO foo (my_array) SELECT DISTINCT '{TEST}';^HINT: You will need to rewrite or cast the _expression_.It's easy enough to add a cast, but I was curious if this was expected and desired behavior. Thanks.Ken--AGENCY SoftwareA Free Software data systemBy and for non-profitslearn more about AGENCY orfollow the discussion.--AGENCY SoftwareA Free Software data systemBy and for non-profitslearn more about AGENCY orfollow the discussion.--AGENCY SoftwareA Free Software data systemBy and for non-profits(253) 245-3801learn more about AGENCY orfollow the discussion.
