This is a discussion on python - ctl: Comment subsequent non-spaces after value. within the pgsql Committers forums, part of the PostgreSQL category; --> Log Message: ----------- Comment subsequent non-spaces after value. In cases where trailing non-space data exists, config would introduce a ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Log Message: ----------- Comment subsequent non-spaces after value. In cases where trailing non-space data exists, config would introduce a syntax error: # foo = bar something that should likely be commented When 'foo' is set to another value or simply uncommented, it would introduce a syntax error: foo = bar something that should likely be commented So, comment post value non-space to produce something that won't cause an error: foo = bar #something that should likely be commented While config does it's best to touch as little as possible, if it does need to change something, it is important to make sure that it doesn't render an erroneous configuration file. Modified Files: -------------- ctl/src: config.py (r1.1.1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvs...1.1.1.1&r2=1.2) ctl/test: config.py (r1.1.1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvs...1.1.1.1&r2=1.2) ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match |
| Thread Tools | |
| Display Modes | |
|
|