#170 postgresql patch for user preferences

closed-accepted
5
2002-03-03
2002-02-23
Nick Sayer
No

This patch changes the name of the 'user' column to
'username' and replaces the 'replace' syntax with a
delete and an insert done in a transaction.

A perhaps mysql friendly version of the patch would use
the transaction for postgres and replace for mysql
depending on the type of database specified, I suppose.

Discussion

  • Nick Sayer

    Nick Sayer - 2002-02-23

    postgresql patch for userprefs db backend

     
  • Anonymous - 2002-02-24
    • assigned_to: nobody --> simond
     
  • Simon Dick

    Simon Dick - 2002-02-24

    Logged In: YES
    user_id=30544

    Thanks, I did actually notice this a few days before 1.2.5
    was due out, hence why there's a note about it in the
    db-backend.txt file. Your patch would work, but on the other
    hand would break compatibility for people who are currently
    using a MySQL database with the old column name. I am
    planning to alter the db prefs so you can specify each
    column name before 1.2.6 and make the REPLACE optional. I'll
    set this patch to postponed until I get it working.

     
  • Simon Dick

    Simon Dick - 2002-02-24
    • status: open --> open-postponed
     
  • Simon Dick

    Simon Dick - 2002-03-03
    • status: open-postponed --> closed-accepted
     
  • Simon Dick

    Simon Dick - 2002-03-03

    Logged In: YES
    user_id=30544

    OK, working support for PostgreSQL as a prefs backend is now
    in the CVS version of SquirrelMail. Thanks for your patch,
    it was used (with some modifications to keep MySQL working :)

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks