I was getting postgresql syntax errors running SMW_refreshdata recently:
...
Database returned error "1: ERROR: syntax error at or near ""t1""
LINE 1: ...rchyQuery 127.0.0.1 */ OR REPLACE FUNCTION create_"t1"() RET...
It boils down to the getCreateTempIDTableSQL being passed a quoted and escaped
On Wed, 18 May 2011 00:35:45 Jeroen De Dauw wrote:
> Hey,
>
> > So what you'll need to do is install SMW 1.5, ...
>
> I highly discourage you, or anyone else, to run SMW 1.5. It has known
> security vulnerabilities, which have been fixed in following releases. The
> current stable version is 1.5.
On Tue, 17 May 2011 00:39:19 Jeroen De Dauw wrote:
> I don't understand what you are trying to say; can you rephrase?
Ok. As I recall, a from scratch SMW install on a postgres based mediawiki
instance worked in previous versions without a problem — though the unused
properties page was broken.
On Sun, 15 May 2011 11:34:18 Jeroen De Dauw wrote:
> Hey,
>
> I just set up a wiki (from trunk) with PostGres to find and fix the PG
> issues in SMW. I found one during the SMW table setup that was easily fixed
> [0]. I've imported a bunch of data in my wiki and can run queries without
> getting a
On Fri, 08 Apr 2011 05:43:41 you wrote:
> On 07/04/11 15:09, Jeroen De Dauw wrote:
> ...
>
> > Note that SMW trunk is currently not so stable due to significant
> > refactoring for SMW 1.6.
>
> In fact, there are so significant changes to the datatype system going
> on that I do strongly encourag
On Fri, 08 Apr 2011 02:09:50 you wrote:
> Hey,
>
> I'm waiting for the PostGres support on MW 1.17 to be fixed before
> attempting to solve these issues. This is taking quite a long time
> unfortunately... Do feel free to have a go at it yourself though.
Both of the bugs I cited have patches. The
What can we do to expedite the fixing of the various postgresql problems; in
particular:
26202 Semantic MW fails due to syntax error in PostgreSQL
19948 Special:UnusedProperties produces database error for PostgreSQL
I'd like to switch to using SVN trunk to help test other bug fixes I've
submi
