similar to: Oracle and Postgresql support in the query_analyzer plugin

hi, I started today to use the acts as taggable plugin and it''s working as expected. I added a method find_tagged_with_all since I needed to find the elements tagged with all the items in a list while find_tagged_with finds all the elements tagged with any of the list terms. Attached to this mail there''s a patch which adds the find_tagged_with_all method and which solves a

On 19/05/2019 15:42, mabi via dovecot wrote: > ??????? Original Message ??????? > On Sunday, May 19, 2019 2:58 PM, John Fawcett via dovecot <dovecot at dovecot.org> wrote: > >> I guess it is not supported for PostgreSQL or Sqlite, since they don't >> have "ON DUPLICATE KEY UPDATE" statement which is what is being used in >> MySQL. > That's it,

On 19/05/2019 12:52, mabi via dovecot wrote: > Hello, > > I am trying to setup the last_login plugin on Dovecot 2.3 in order to log a user's last IMAP login into a separate PostgreSQL table called last_login. I am actually following that guide: https://docs.iredmail.org/track.user.last.login.html with the exception that I use PostgreSQL instead of MySQL. > > So far it works at

> On 19 May 2019 16:42 mabi via dovecot <dovecot at dovecot.org> wrote: > > > ??????? Original Message ??????? > On Sunday, May 19, 2019 2:58 PM, John Fawcett via dovecot <dovecot at dovecot.org> wrote: > > > I guess it is not supported for PostgreSQL or Sqlite, since they don't > > have "ON DUPLICATE KEY UPDATE" statement which is what

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 22 May 2019, John Fawcett via dovecot wrote: > an update when insert fails seems to be a MySQL specific extension to > standard Sql. So I think that it's clear that support for PostgreSql and > Sqlite? needs to be implemented. The same issue likely exist in other > plugins too, for example expire. > > My doubts are

Dear all, I'm trying to get last_login plugin working with PostgreSQL, but seems Dovecot doesn't handle duplicate key while updating last login time (note: same setting works fine with MariaDB). I wonder whether it's a bug of Dovecot or i should handle this with PostgreSQL trigger. OS: OpenBSD 6.4 (amd64) Dovecot: 2.2.36 PostgreSQL: 10.5 Error log: ################### Mar 31

Hello, I am trying to setup the last_login plugin on Dovecot 2.3 in order to log a user's last IMAP login into a separate PostgreSQL table called last_login. I am actually following that guide: https://docs.iredmail.org/track.user.last.login.html with the exception that I use PostgreSQL instead of MySQL. So far it works at least for the very first login of a user but it looks like Dict

??????? Original Message ??????? On Sunday, May 19, 2019 2:58 PM, John Fawcett via dovecot <dovecot at dovecot.org> wrote: > I guess it is not supported for PostgreSQL or Sqlite, since they don't > have "ON DUPLICATE KEY UPDATE" statement which is what is being used in > MySQL. That's it, PostgreSQL does not have "ON DUPLICATE KEY" but instead uses

A new release of the puppetlabs/postgresql module is now available on the Forge: https://forge.puppetlabs.com/puppetlabs/postgresql/2.1.0 Changelog ======== This release is primarily a feature release, introducing some new helpful constructs to the module. For starters, we''ve added the line `include ''postgresql_conf_extras.conf''` by default so extra parameters not

On 28.5.2019 22.34, mabi via dovecot wrote: > ??????? 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). >>

??????? Original Message ??????? On Monday, May 20, 2019 12:37 AM, John Fawcett via dovecot <dovecot at dovecot.org> wrote: > So looking into this with a postgresql databse to work with: the above query does not work. You have to specify either the column name or the constraint name that you expect to be violated in order for the update to take place. > > With a map like this one

??????? 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

On 21/05/2019 15:45, mabi via dovecot wrote: > ??????? Original Message ??????? > On Monday, May 20, 2019 12:37 AM, John Fawcett via dovecot > <dovecot at dovecot.org> wrote: > >> So looking into this with a postgresql databse to work with: the >> above query does not work. You have to specify either the column name >> or the constraint name that you expect to

I'm currently experiencing a problem which has already been described by Jonathan in http://www.dovecot.org/list/dovecot/2006-August/015501.html If I use CRAM-MD5 auth with passwd-file as a backend (Thunderbird client) everything works fine (MD5-hashes have been shortened for readability): dovecot: auth(default): password(bob at foo.bar,10.0.0.123): Credentials: f12c884ba3cc82.. dovecot:

Is it possible to use the dovecot 1.1 expire plugin with postgresql and if so how?

The wiki entry at http://wiki.dovecot.org/Plugins/Expire needs an update for Dovecot 1.2 and PostgreSQL: -- v1.2+: CREATE OR REPLACE FUNCTION merge_expires() RETURNS TRIGGER AS $$ BEGIN IF exists(SELECT 1 FROM expires WHERE username = NEW.username AND mailbox = NEW.mailbox) THEN UPDATE expires SET expire_stamp = NEW.expire_stamp WHERE username = NEW.username AND mailbox = NEW.mailbox;

Hi, I have tried to implement last_login with PostgreSQL and I found an old thread from June 2019. I have found a simple solution that I want to share with you: I followed the instructions on how to set up a last_login on the official documentation. Therefor I creates a very simple table having userid and last_login fields. Added plugin and dict information. I received the duplicate key errors

Dear list - I am having a problem using RODBC to access records from tables in a PostgreSQL database. There is no problem establishing the connection using chnl <- odbcConnect (dsn= ... etc. The DSN seems to be properly set up using the PostgreSQL Unicode ODBC driver, and sqlTables(chnl) works OK and produces a list of tables in the database (they are all in a schema called 'source').

CentOS Errata and Security Advisory 2012:0678 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-0678.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 84ec4f5147f1794dedf496cb3be490a0ded24073018e92cd3a4c931a7d9598dc postgresql-8.4.11-1.el6_2.i686.rpm

CentOS Errata and Security Advisory 2012:1037 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-1037.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: ac5806bdf1eafdb0d494f1c9fa3f0db6d7bb7a7341846c7f79cc2875f5c6357a postgresql-8.4.12-1.el6_2.i686.rpm