Re: Thoughts on using Text::Template for our autogenerated code?

From: John Naylor <john(dot)naylor(at)enterprisedb(dot)com>
To: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Daniel Gustafsson <daniel(at)yesql(dot)se>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Thoughts on using Text::Template for our autogenerated code?
Date: 2023-03-31 03:32:04
Message-ID: CAFBsxsEkVF98JcND+5hh8RQf1KOYRzjFFD0PC=fkR7EZMtEuhA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Mar 31, 2023 at 4:15 AM Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
wrote:
> For those who already responded, are your concerns limited to the
dependency issue? Would you have concerns about a templating library that
was developed by us and included in-tree?

Libraries (and abstractions in general) require some mental effort to
interface with them (that also means debugging when the output fails to
match expectations), not to mention maintenance cost. There has to be a
compensating benefit in return. The cost-to-benefit ratio here seems
unfavorable -- seems like inventing a machine that ties shoelaces, but we
usually wear sandals.

--
John Naylor
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2023-03-31 03:54:31 Re: Option to not use ringbuffer in VACUUM, using it in failsafe mode
Previous Message Peter Smith 2023-03-31 03:01:57 Re: Data is copied twice when specifying both child and parent table in publication