cubicweb #769060 # # skip registered procedure using an unavailable extension language [open]
The latest versions of CW will execute _regproc_bss.postgres.sql at db-create time, which fails on windows+postgresql (because plpythonu is not always installed). Do we really need these stored procedures in CW or would they rather belong to a cube ? Simple tests on windows seem to indicate that the pg installed (version 8.3.8) proposes to install plpythonu, though there is a Python version dependency that needs to by checked. This needs to be investigated. | |
priority | normal |
---|---|
type | bug |
done in | <not specified> |
load | 0.500 |
load left | 0.500 |
closed by | <not specified> |
similar entities
- cubicweb #813913 log-file preference in all-in-one.conf not taken into account on windows
- cubicweb #959526 [tests] database locked error when running unittests on windows
- cubicweb #197651 run behind Microsoft IIS
- Running CubicWeb on Windows
- TheCubicWebBook #541389 installation from debian package
[see all]
Comments
-
2010/03/22 09:57, written by sthenault
-
2010/03/22 11:25, written by acampeas
-
2010/03/26 13:18, written by sthenault
- ask weither we should install the extension on db-create
- skip registered procedure using an unavailable extension language
-
2010/03/31 14:00, written by acampeas
-
2010/03/31 14:10, written by sthenault
-
2010/03/31 14:14, written by acampeas
-
2010/03/31 14:22, written by mailbot
add commentimo the BytesFileSystemStorage definitly belong to cubicweb itself. My question would rather be : why do we skip plpython installation under windows platforms?
that just got a fix
but what about sqlserver/mysql users ?
downgrading to normal: cw 3.7.2 doesn't use anymore plpythonu extensions.
At some point we should:
Alexandre: didn't you have a fix for plpython/windows finally ?
see my comment on 2010/03/26
do you suggest we rename this ticket ?
would be better indeed