When someone has remove a unit because going out of country with a point, I got this message on my webpage
"A SQL query failed, if this problem persists please inform the admin. This problem has been recorded and will be processed by a developer asap."
Here is the errorlog.txt
ERROR: current transaction is aborted, commands ignored until end of transaction block
GMT+0 Time:17:46 Wed 13th
Client's IP: 207.35.50.100
Line: 57
Variable dump:
It looks like PostgreSQL is failing somewhere before that query, but the error isn't being picked up until it reaches the first sql_put() function. I'd tell you to hold tight for a couple of weeks for the new version, but unfortunately the new version is dropping support for PostgreSQL for the time being.
Also I've made a few bug fixes since 0.72a, some of which do involve the unit placement phase (mostly to do with orders), so it might just take an upgrade to the latest 0.72 release to fix.
If your installation has a lot of users I'll try to make time to add support for PostgreSQL in 0.75, e-mail me or add me in MSN at kestas.j.k@gmail.com , and I'll try to walk you through sorting this out.
Regards,
Kestas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anyone has a clue?
When someone has remove a unit because going out of country with a point, I got this message on my webpage
"A SQL query failed, if this problem persists please inform the admin. This problem has been recorded and will be processed by a developer asap."
Here is the errorlog.txt
ERROR: current transaction is aborted, commands ignored until end of transaction block
GMT+0 Time:17:46 Wed 13th
Client's IP: 207.35.50.100
Line: 57
Variable dump:
Array
(
[this] => database_pgsql Object
(
[sqllink] => Resource id #20
[putqueries] => 11
[getqueries] => 80
)
[sql] => DELETE FROM messages
WHERE messageid=273
[HTML] => html Object
(
[scriptstarttime] => 0.78572700 1166031985
)
[SECURITY] => security Object
(
[errorlog] => Resource id #17
)
)
Cedric
Hello Cedric,
It looks like PostgreSQL is failing somewhere before that query, but the error isn't being picked up until it reaches the first sql_put() function. I'd tell you to hold tight for a couple of weeks for the new version, but unfortunately the new version is dropping support for PostgreSQL for the time being.
Also I've made a few bug fixes since 0.72a, some of which do involve the unit placement phase (mostly to do with orders), so it might just take an upgrade to the latest 0.72 release to fix.
If your installation has a lot of users I'll try to make time to add support for PostgreSQL in 0.75, e-mail me or add me in MSN at kestas.j.k@gmail.com , and I'll try to walk you through sorting this out.
Regards,
Kestas