From: | Daniel Schuchardt <daniel_schuchardt(at)web(dot)de> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | david(at)fetter(dot)org |
Subject: | Re: operator varchar = integer |
Date: | 2008-05-05 15:26:40 |
Message-ID: | 481F2730.2010401@web.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
David Fetter schrieb:
> That technical debt is a risk to your whole project, and you need to
> dedicate resources to paying it down.
>
> <http://en.wikipedia.org/wiki/Technical_debt>
>
> There are ways to get those automated casts, but they will only make
> your situation worse in the long run.
>
> Cheers,
> David.
>
*g* interesting standpoint and your right but:
it is impossible for us to find all the points where the new 8.3
behavoir would crash at the first time. so our next versions would be
very buggy and our customers wouldn't be happy ;-)
the next problem is that our service personal has to be traineed too;
they dont know much about casting, 81 does it automatically; problems
problems problems.
if it is not possible (i know it is) ;-) to recreate automatic casts in
83 we would not be able to upgrade to 83 the next years. the next
possible date would be in about 3-4 years with the next major release.
PS:
our db has about 500 functions, 300 tables, 1000 indexes, 1200 Views
that all use implicit casting.
and: everything is working fine ;-) :-P
so we have to choose another way.
cheers.
From | Date | Subject | |
---|---|---|---|
Next Message | Lee Feigenbaum | 2008-05-05 15:30:29 | Re: bytea and character encoding when inserting escaped literals |
Previous Message | Dan Myers | 2008-05-05 15:26:22 | Re: Custom C function - is palloc broken? |