The mailing list for listmasters using Sympa

[David Verdin <address@concealed>]

Hi Dan,

I didn't see any reply to your mail but I can still give you some informations.

• First: Yes, some users use Postgres with Sympa. Actually, it was the second most used RDBMS in the beta test (7 people test Sympa 6.0 beta with Postgres).
• Second: Sympa automatically upgrades the database structure for MySQL and SQLite, because the Sympa authors use MySQL and we have very active contributors for SQLite, the helped us create the automatic check of database for this RDBMS. We didn't receive such a contribution for postgres, so there is no automatic upgrade for it. However, we provide an SQL query that creates the database (it can alos be used for upgrades) for all the supported RDBMS, and beta test allowed us to check that Sympa runs well with them.
• Third: we plan to improve support of the RDBMS in future releases by creating automatically the DB creation query. This could be a first step towards a full support of the upgrade.
• Finally: it looks like you did some debugging about this issue. I'd love to read more about it. Why not sending us your version on Upgrade.pm, so that we could add your fixes to the next stable release?

Best regards,

David Verdin

Le 09/03/2010 20:53, Dan Pritts a écrit :

address@concealed">

Hi,

if you are successfully using postgres/EnterpriseDB with sympa 6.x
please reply.  

Details:

We use EnterpriseDB, a commercial product based on postgresql.  In the
interest of keeping everything on one db platform I'm working to put
our new sympa 6.0.1 installation on enterprise DB.

I've run into one issue.  For some reason, connecting to Enterprise DB, the 
postgres schema name is being returned as "public" including double quotes,
rather than public without quotes.  This doesn't appear to break sympa
operations but does break the database check in Upgrade.pm. 

e.g., the contents of $dbh->tables looks like:

 "public".admin_table

rather than

 public.admin_table

This was simple to fix once I found the existing check for table names
with public. prepended in Upgrade.pm.


More importantly, while debugging this, I noticed lots of explicit
checks for table structure and such with MySQL and SQLite, but nothing
so specific for any of the other "supported" databases.

I am guessing that the core development team uses mysql and sqlite but not
the other databases.  This makes me nervous - I do not want to be
running an important service on a poorly-supported database platform.

I am not religious about EnterpriseDB/Postgres, if necessary I'll just 
use MySQL for sympa.  However, I would prefer to use EnterpriseDB if it's
not too much work.

So, if you are using Postgres with sympa 6, please reply.

thanks!
danno
--
Dan Pritts, Sr. Systems Engineer
Internet2
office: +1-734-352-4953 | mobile: +1-734-834-7224

Internet2 Spring Member Meeting
April 26-28, 2010 - Arlington, Virginia
http://events.internet2.edu/2010/spring-mm/
  

-- 
David Verdin
Comité réseau des universités