search for: tablename_pkey

...pattern = shared/last-login/$user/$domain table = last_login value_field = last_login value_type = uint fields { username = $user domain = $domain } }| there's no field name that is obviously the primary key. I've reworked the patch to use the postgres default primary key constraint name (tablename_pkey). The attached fix should work in that case, although I feel it's not general enough. John -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20190520/6d0f6850/attachment-0001.html> -------------- next part...

...ld = last_login > value_type = uint > > fields { > username = $user > domain = $domain > } > } > > there's no field name that is obviously the primary key. I've reworked the patch to use the postgres default primary key constraint name (tablename_pkey). So as you mention the new query you adapted which includes the primary key works, I tested it manually against PostgreSQL 10.5. > The attached fix should work in that case, although I feel it's not general enough. Unfortunately my compiling skills are quite poor and I did not manage to...

??????? Original Message ??????? On Monday, May 20, 2019 12:37 AM, John Fawcett via dovecot <dovecot at dovecot.org> wrote: > there's no field name that is obviously the primary key. I've reworked the patch to use the postgres default primary key constraint name (tablename_pkey). > > The attached fix should work in that case, although I feel it's not general enough. I saw there has been quite some discussion how to make things more generic and better for database queries in general in Dovecot around my issue but I would still be very thankful if your original p...

...essage ??????? > On Monday, May 20, 2019 12:37 AM, John Fawcett via dovecot > <dovecot at dovecot.org> wrote: > >> there's no field name that is obviously the primary key. I've >> reworked the patch to use the postgres default primary key constraint >> name (tablename_pkey). >> >> The attached fix should work in that case, although I feel it's not >> general enough. >> > I saw there has been quite some discussion how to make things more > generic and better for database queries in general in Dovecot around > my issue but I would s...

...st_login >> value_field = last_login value_type = uint fields { username = $user >> domain = $domain } }| >> >> there's no field name that is obviously the primary key. I've >> reworked the patch to use the postgres default primary key constraint >> name (tablename_pkey). >> > So as you mention the new query you adapted which includes the primary > key works, I tested it manually against PostgreSQL 10.5. >> >> The attached fix should work in that case, although I feel it's not >> general enough. >> > Unfortunately my comp...

On 19/05/2019 20:31, mabi via dovecot wrote: > > ??????? Original Message ??????? > On Sunday, May 19, 2019 7:36 PM, John Fawcett via dovecot > <dovecot at dovecot.org> wrote: >> >> Attached is a tentative patch. I've verified no regression for mysql. >> There should be no regression for sqlite as the code path is identical. >> >> Are you able to