| From: | Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr> |
|---|---|
| To: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
| Cc: | pgadmin-hackers(at)postgresql(dot)org |
| Subject: | Re: Feature requests after crash |
| Date: | 2002-02-22 14:00:08 |
| Message-ID: | 200202221400.g1ME08FP011535@www1.translationforge |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
> my_sum(int4, int4)
> "My_Sum"(int4, int4)
> My_Sum(int4, int4)
Yes, but such a redundancy would be detected, which is ***better*** than
nothing. We can then issue a warning instead of "blocking everything".
Furthermore, many names are not case sensitive because of SQL (tables,
views), which makes ILIKE the perfect solution to track dependencies :
tables<->views, views<->functions, tables<->functions, etc...
+ we are only looking for one-level depencies.
This is quite easy to implement using pgSchema... I am
testing ALTER TRIGGER wich will be available tonight.
Cheers,
Jean-Michel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jean-Michel POURE | 2002-02-22 15:34:58 | Update trigger name |
| Previous Message | Dave Page | 2002-02-22 13:31:56 | Re: Feature requests after crash |