John McNally wrote:
> Colm McCartan wrote: > >>John McNally wrote: >> >> >>>I would recommend the head of 2.x tree over 2.1, but better yet try >>>using the code in the standalone torque repo. And there is no need to >>>have webmacro for torque, are you using it for your application screens? >>> >>The standalone torque repo - excuse my ignorance but does this include a >>full version of turbine? How does it differ from the turbine-2 repo? >> >>I am not using webmacro at all - I went through and binned a lot of the >>webmacro-related files in places like turbine/modules/actions. Also >>python stuff etc. Perhaps I messed up the inital build which I know >>should detect which optional jars are present - but am I right in >>thinking that it doesn't do this test for webmacro? >> > > How about trying the unofficial tdk distribution that Martin just > posted. I do not use the tdk, so I cannot be much help with its > processes. I am interested in being able to drop debug code into the source, step through it at debug time etc. Is the standalone torque, as it suggests, totally seperate from turbine? Does anyone else have positive experiences from using postgres with 2.x? > I do not have postgresql working, but I thought jason (and likely > others) test the tdk against it, so I do not understand how they would > not work. But patches are welcome. I'd be delighted to submit patches if I can get anywhere near it working.. It may be, of course, that I have confused the build process somewhere. >>In a previous post I also mentioned the bad foreign key references that >>are generated when an alias to the turbine_user table is specified in >>the torque schema. > > i have not had time to fix this and i keep hoping to come up with > something better than the current not very impressive hack. If you have > a fix, please share it. Again I'd like to help - I have ended up manually generating the db. I wasn't even sure if this was a known issue. Is there a public bug db for turbine anywhere? Thanks a lot for the response, colm -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
