[Tickets #14964] Re: Postgresql12 dropped adsrc

[noreply at bugs.horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: https://bugs.horde.org/ticket/14964
------------------------------------------------------------------------------
  Ticket           | 14964
  Aktualisiert Von | heinz at htl-steyr.ac.at
  Zusammenfassung  | Postgresql12 dropped adsrc
  Warteschlange    | Components
  Typ              | Bug
  Status           | Unconfirmed
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


mail at webthatworks.it (2019-11-20 23:34) hat geschrieben:

I opened a pull request on github with a patch that should solve the  
problem, it's there waiting for some love.


> I can confirm that bug.
>
> I'm trying to fix it and I'll submit a patch ASAP on github.
>
> I've talked with the postgresql guys and it seems that that column  
> has been deprecated for a long time and it even risked to contain  
> stale data.
>
> They have suggested me to use pg_get_expr(adbin,adrelid), but on  
> overall the current queries that use adsrc are a bit fragile and  
> could use information_schema rather than interrogating pg specific  
> columns and massaging strings.
>
> Currently I've some tentative code but I'm not able to replicate  
> EXACTLY the return of one of the queries.
> namely original query return eg.
>
> nextval('public.horde_alarms_id_seq'::regclass)
>
> while mine returns
>
> nextval('horde_alarms_id_seq'::regclass)
>
> I'm going to subscribe to horde dev mailing list and propose some  
> patch on github ASAP
>