Hi Dave,
I know it's far from top priority feature, but I use it occasionally in
pgAdmin3. It works, at least the part the admin tool is used for.
As you noted, it's not the creation, but maintenance, or better said -
quick check when cryptic errors complain about missing operator for type
A and B, and we're pretty sure we've covered both ;)
Of course, if I'm the only one, there's no point to make the effort.
Maybe few others will pop-up eventually, or, perhaps, my team and I find
some time and help you guys build the feature. That's the beauty of open
source, right :)
Thanks for the quick reply.
BR,
Milan Oparnica
On 1.8.19. 10:21, Dave Page wrote:
Hi
On Wed, Jul 31, 2019 at 4:02 PM Milan Oparnica <milan....@gmail.com
<mailto:milan....@gmail.com>> wrote:
Hello,
I like the fresh and modern approach that pgAdmin4 offers,
updating instantly when new versions pop-up praying to find few
options I still miss from pgAdmin3.
Working with 'Operators' objects
====================
Is there any chance you could reconsider the decision not to
support Operators objects in pgAdmin4 ?
I'm sure we're not the only one to use them - as they proved to be
a great tool when migrating software from other database platforms.
I think you're the only one to have asked for them. Unfortunately it's
non-trivial code, and I'm pretty sure it was actually broken in pgAdmin 3.
They provide easiest way of handling certain date and string
crucial operations that differ from pg implementation.
Sure, but does having the UI in pgAdmin really buy you much? I assume
you're creating them extremely infrequently.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
