| From: | Alex Aquino <alex(at)efficiencygeek(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Are stored procedures/triggers common in your industry |
| Date: | 2022-04-20 20:43:48 |
| Message-ID: | CABxei-0tRjt3PuNW8NfQ8DwL9nmSeXdJPdF2iVqCt19TgSRdzQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Agree on the lock in comment, however, can't we say that of anything one is
dependent on in the tech stack, whether that be at the java vs javascript
vs python, or now aws vs azure vs gcp?
Have always wondered that lock in concern seems to be only mentioned in
light of dbs, but not any other piece of the tech stack.
On Wed, Apr 20, 2022 at 3:31 PM Ravi Krishna <srkrishna(at)vivaldi(dot)net> wrote:
> >I've really only ever worked in web development. 90+% of web
> >developers regard doing anything at all clever in the database with
> suspicion.
>
> One common argument they use is that if you write your business logic in
> stored procedure, you are locked to that database since stored procedure
> languages are pretty much vendor locked.
>
> TBH when one sees tens of thousands of Oracle PL/SQL code, there is some
> truth in this.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Huan Ruan | 2022-04-20 21:12:20 | Re: PITR and Temp Tables |
| Previous Message | Ravi Krishna | 2022-04-20 20:31:01 | Re: Are stored procedures/triggers common in your industry |