Re: pgAdmin can't create Expression Indexes - Mailing list pgadmin-support

I'm afraid I agree with this. Also, with my most recent concern, I found that I was posting an issue to the tracker,
thenresponding by email to individuals from the mailing list who offered possible solutions. Some of the potentially
usefulinformation ended up in the tracker, but much of it got lost in emails that were more or less private. The record
ofwhat did and did not finally solve the problem is scattered about, not in a single place.
 

2 cents.

>  -------Original Message-------
>  From: Michel Feinstein <michelfeinstein@gmail.com>
>  To: Ray O'Donnell <ray@rodonnell.ie>
>  Cc: Aditya Toshniwal <aditya.toshniwal@enterprisedb.com>, pgadmin-support lists.postgresql.org
<pgadmin-support@lists.postgresql.org>
>  Subject: Re: pgAdmin can't create Expression Indexes
>  Sent: 15 May '19 05:10
>  
>  Well, I did a quick look at it and I could see it indeed has more
>  options... But for external people (like me) it seems more complicated
>  to file Issues and keep track of them.
>  
>  On Github I would open the project's page, open a new issue, and every
>  time there is a new message for my issue (and only my issue) I will be
>  notified by email. If anyone wants to know what we spoke about it, all
>  the thread is right there on the Issue page.
>  
>  But currently if I want to file a bug or a feature I have to enroll to
>  an email list to communicate it, so I will receive messages for
>  everything, every day, which is not in my interest, so I will
>  unsubscribe from this mailing list and stop receiving messages for
>  everything, including the only think I care about. If I want to check
>  what was argued about an issue in the past, I have to search into
>  several emails, not as clean as an Issue thread. Also, I didn't have
>  to login to file a bug report, I could set the priority, assign it to
>  people, I had apparently lots of control over it. Not even to mention
>  the interface seems bulky and outdated (but this is minor aesthetics,
>  so I don't take this seriously).
>  
>  Github Issues aren't as complete, but I think it has enough, you can
>  set it to a milestone, label it, assign it to people, automatically
>  close it with a commit and a pull request, easy to see, follow and
>  track what's related to it... All of it with user access control, on
>  who can do what... But if your current system has more stuff and you
>  like it, it's fine, it's just gave me the appearance of being
>  clunkier, and definitely not as easy for someone from outside of the
>  project to jump-in, report, jump-out and get eventual updates.
>  
>  Best wishes,
>  
>  Michel.
>  
>  On Wed, May 15, 2019, 05:31 Ray O'Donnell <ray@rodonnell.ie> wrote:
>  
>  > On 15 May 2019 06:59:11 Michel Feinstein <michelfeinstein@gmail.com>
>  > wrote:
>  >
>  >> I will...but just to add my 2 cents, it would be a lot better if
>  >> you guys could move to Github and use their Issue system instead.
>  >
>  > Why? - Just curious.
>  >
>  > Ray.
>  >
>  > On Wed, May 15, 2019 at 1:43 AM Aditya Toshniwal
>  > <aditya.toshniwal@enterprisedb.com> wrote:
>  >
>  > Hi,
>  >
>  > On Wed, May 15, 2019 at 7:46 AM Michel Feinstein
>  > <michelfeinstein@gmail.com> wrote:
>  >
>  > I can't find a way to create an Expression Index such as:
>  > Yes, it's not there. You can raise a feature request here -
>  > https://redmine.postgresql.org/projects/pgadmin4/issues
>  >
>  > CREATE UNIQUE INDEX idx_lower_unique
>  > ON your_table (lower(the_column));
>  >
>  > Am I missing something or does pgAdmin really doesn't support it?
>  >
>  > Best wishes,
>  >
>  > Michel.
>  >
>  > --
>  >
>  > Thanks and Regards,
>  > Aditya Toshniwal
>  > Software Engineer | EnterpriseDB India | Pune
>  > "Don't Complain about Heat, Plant a TREE"
>  
>