Changes between Version 4 and Version 5 of PgSchemaPatch

Show
Ignore:
Author:
pacopablo (IP: 71.111.186.77)
Timestamp:
05/29/06 00:20:11 (1 year ago)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • PgSchemaPatch

    v4 v5  
    22 
    33[[html(<div id="newsflash">)]] 
    4  * Wahoo! The PgSchemaPatch was accepted into trunk as of [T:changeset:3249. 3249] 
     4 * Wahoo! The PgSchemaPatch was accepted into trunk as of [T:changeset:3249 3249] 
    55[[html(</div>)]] 
    66 
    88 
    99Patch provides the ability to use a schema for each trac site instead of a full database instance 
    10  
    11 More info can be found at: http://embassy.asylumware.com/projects/trac/wiki/Patches/Schema 
    1210 
    1311== Bugs/Feature Requests ==  
    3129Simply apply the patch: 
    3230{{{ 
    33 cd path/to/trac/src/trac-0.9.3 
    34 patch -p1 < trac-0.9.3-schema.patch 
     31cd path/to/trac/src/trac-0.9.5 
     32patch -p0 < pgschemapatch-0.9.5.patch 
    3533python setup.py install 
    3634}}} 
    3735 
    38 Then when creating a new site, append the schema name to the PostgreSQL DB URIas in the example below: 
     36Then when creating a new site, append the schema name to the PostgreSQL DB URIs in the example below: 
    3937{{{ 
    4038trac-admin initenv new_proj postgres://myuser@localhost/mydb?schema=my_schema /var/svn/new_proj /usr/share/trac/templates