RE: Are stored procedures/triggers common in your industry - Mailing list pgsql-general

From Basques, Bob (CI-StPaul)
Subject RE: Are stored procedures/triggers common in your industry
Date
Msg-id DM8PR09MB63423C342B31E7A4D1BC3D59F7F59@DM8PR09MB6342.namprd09.prod.outlook.com
Whole thread Raw
In response to Are stored procedures/triggers common in your industry  (Guyren Howe <guyren@gmail.com>)
List pgsql-general

We’ve used them in the past, but sparingly.  Usually if the data is abstracted nicely for loading into the DB, you can get away with most processes only needing SQL, at least in our cases.  There are obvious exceptions for things like monitoring or logging.

 

Our use has been for running some setup scripts (with PERL) to generate some derivative CAD models from the PG DB on the fly, but that was a real specific process need.

 

Bobb

 

 

 

My machine - - - PW19-S295-C024

 

From: Guyren Howe <guyren@gmail.com>
Sent: Wednesday, April 20, 2022 2:18 PM
To: pgsql-general@lists.postgresql.org
Subject: Are stored procedures/triggers common in your industry

 

Think Before You Click: This email originated outside our organization.

 

I’ve really only ever worked in web development. 90+% of web developers regard doing anything at all clever in the database with suspicion.

 

I’m considering working on a book about implementing business logic in Postgres, and I’m curious about how common that actually is.

pgsql-general by date:

Previous
From: Rob Sargent
Date:
Subject: Re: Are stored procedures/triggers common in your industry
Next
From: Philip Semanchuk
Date:
Subject: Re: Are stored procedures/triggers common in your industry