#1087 closed defect (invalid)
Report execution failed: near "as": syntax error
Reported by: | akhavr | Owned by: | Russ Tyndall |
---|---|---|---|
Priority: | high | Component: | TimingAndEstimationPlugin |
Severity: | major | Keywords: | |
Cc: | Trac Release: | 0.10 |
Description
After trunk installation, all reports fail with
Report execution failed: near "as": syntax error
I set this to blocker since w/o reporting this very needed plugin is not quite useful.
Attachments (0)
Change History (5)
comment:1 Changed 18 years ago by
Priority: | normal → high |
---|---|
Severity: | blocker → major |
comment:2 Changed 18 years ago by
Configuration:
- trac 0.10
- timingandestimationplugin/trunk (from distribution zip file)
- standart sqllite backend
- python-module-pysqlite-1.0
- sqlite-2.8.16
There only couple plugins installed, so it cannot be an interference with others.
This happens with all reports.
comment:3 Changed 18 years ago by
Resolution: | → invalid |
---|---|
Status: | new → closed |
Per the Supported Versions section of the documentation. Sqlite 3.2.3 or greater is neccessary to use this plugin.
I believe the postgres backend is also fully functional at this point, if that is a better route for you.
Hope this helps,
Russ
comment:4 Changed 18 years ago by
also I think you might need pysqlite2, but I am not so sure about the version of that neccessary
comment:5 Changed 18 years ago by
I have exactly the same problem: our server uses sqlite-2.8.16. We're running RHEL 4 and are dependent on using the versions of packages that are available via the redhat channel (because we choose to let them manage security patches and compatibilities).
Too bad!
Can you give me any more help?
Many other people are successfully running this plugin, so I have to assume this is something specific to your setup. It looks like possibly the backend you are using does not support column aliasing with the 'as' syntax.
Thanks for the help,
Russ