Dne Fri, 18 May 2007 22:42:57 -0700
"Chris Travers" <[EMAIL PROTECTED]> napsal(a):
> Hi all;
>
> My ideas here are my own. I do not speak for the core team in this
> but I think that it is important to share my ideas and thoughts with
> everyone and get some feedback.
>
> 1.2.5 has been one of
Hi all;
My ideas here are my own. I do not speak for the core team in this
but I think that it is important to share my ideas and thoughts with
everyone and get some feedback.
1.2.5 has been one of the more problematic releases in some time
(since 1.2.0-1.2.2). I wanted to share my thoughts wit
You probably still need to get the new Form.pm. The problem is not in
the data or the database schema but one of the queries that was
rewritten in order to get better performance on systems with large
databases.
If you need me to, I can send it to you.
Best Wishes,
Chris Travers
On 5/18/07, Vla
Dne Fri, 18 May 2007 12:55:34 -0700
"Chris Travers" <[EMAIL PROTECTED]> napsal(a):
> When issuing an AP transaction in 1.2.5 (only), you may get the
> following error:
>
> ERROR: column "customer_id" does not exist
>
> This problem was caused by a problem with one of the performance
> patches wh
Hi all;
A new problem has been found in 1.2.5's date handling which causes
financial statements to display invalid dates including part of a META
tag setting the page charset to utf-8. This only affects 1.2.5, and
again those who are not affected by the specific problems in 1.2.5 are
advised to w
Chris Travers wrote:
> This bug was corrected in an earlier version. However, it was caused
> by problems in the database creation script. If you are getting this
> error, please contact me for a hotfix sql script to fix your db.
>
> Of if you are familiar with PostgreSQL, run the following comm
When issuing an AP transaction in 1.2.5 (only), you may get the following error:
ERROR: column "customer_id" does not exist
This problem was caused by a problem with one of the performance
patches which made it into 1.2.5. A fix has been committed to SVN
branches/1.2
Anyone experiencing this pr
Hotfix email forthcoming. For those who have not upgraded yet, I
suggest upgrading to 1.2.5 only if you require fixes for those areas
specifically listed in the changelog. Otherwise wait for 1.2.6. THe
fixes in 1.2.5 are major for some users, but do not affect everyone.
On 5/18/07, Charley Tigg
I just upgraded to 1.2.5. It seems that, in that upgrade, I should have
run a particular script to upgrade the database first. Yet, I have no
idea where that script is located. Specifically, when I try to go to AP
-> Add Transaction, I get the following error:
SELECT ct.name AS vendor, ct.c
