| From: | Dmitriy Igrishin <dmitigr(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | jd(at)commandprompt(dot)com, "Rhys A(dot)D(dot) Stewart" <rhys(dot)stewart(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: versioned pl/pgsql functions |
| Date: | 2010-09-21 21:19:06 |
| Message-ID: | AANLkTimnMgC8vYugy58ZonDFssWbbuEtCzW605XzVLGX@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hey all,
After ten years with stored procedures I am thinking so this is not
> too well technique. Much better is writing stored procedures to a file
> and using usual tools for file's versioning. We did some tools for
> storing a versions inside database, but still we prefer a standard
> developer tools - vi or emacs like editor and plain text. The main
> problem of procedures maintained inside database is loss of outer
> formatting and outer comments. And you cannot to group procedures to
> modules. On the other hand - some history can be useful for all
> database objects - not only for stored procedures.
Agree with Pavel.
--
Regards,
Dmitriy
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksey Tsalolikhin | 2010-09-21 21:30:15 | Re: ERROR: cache lookup failed for type 14237017 |
| Previous Message | Guillaume Lelarge | 2010-09-21 21:13:43 | Re: 9.0 pg_database datconfig ? |