Home

CVSAnalY and PostgreSQL

Disclaimer: This is not the main repository, this is a fork which I use in order to fix issues and develop some features that I require and which I would like to see them in upstream, too. However, master is a pristine clone of http://git.libresoft.es/cvsanaly/ and I develop using my own branches, which are also available here.

Testing the Postgresql backend

  • Creating the database. If Postgresql is installed locally and the user is gpoo and the database name is gnome then the following commands should work:

    $ sudo su postgres -c psql
    postgres=# create user gpoo;
    postgres=# create database gnome owner gpoo;

  • Any time you would like to start over again:

    postgres=# drop database gnome;
    postgres=# create database gnome owner gpoo;

  • Create a configuration file (config) with the following content:

    debug = True
    save_logfile = ‘output-pg.log’
    db_driver = ‘postgres’
    db_user = ‘gpoo’
    db_database = ‘gnome’

  • And test it with a small repository as sample, for instance I use gturing:

    $ ./cvsanaly2 -f config /path/to/repo/gturing > gturing-pgsql.log

  • Compare the output of postgres backed against mysql backend.

  • Compare the data stored in both Postgres and MySQL databases.

PostgreSQL/CVSAnalY related bugs

  • Bug 2: PostgreSQL support
  • Bug 28: General view in Database class is not portable
  • Bug 29: Weak referential integrity in MySQL backed

CVSAnalY opened bugs

PostgreSQL Tunning Tips

CVSAnalY and SQLite

SQLite/CVSAnalY related bugs

  • Bug 30: SQLite driver seems broken (ValueError: parameters are of unsupported type)