Number formating

Janeks, I'd be happy to try to help you (and David?) find the answer to your question, by trying to recreate your issue in a similar environment, and then let you know about my results. And potentially also with an actual answer (or confirmation as a "bug"). If appropriate, I'd also add it to my list of additional documentation requests (to be added somewhere in the HELP rpts in the future).

To do so, can you provide some (a bit more) details please, i.e. the relevant steps to recreate your issue by somebody familiar with creating forena rpts using the various report editor features? Eventually by sharing the relevant part of your frx, or sql, etc. If the issue can be created with a (variation of a) sample report, that for sure simplifies things (a) for you to provide more details and (b) for me to actually recreate it.

To be complete: from the sample you gave, I think I do understand the results you actually get, versus the results you would want to get (and I agree it should be as you 'want' them to be). But if I don't understand the issue, I can impossibly try to document or fix it ... right?

Janek, a related question/suggestion: how about using 'round' instead of sprintf, as explained on http://us3.php.net/manual/en/function.round.php

Example #1 there seems to contain a sample similar to your sample (i.e. the 5th in that list), which is this:

echo round(1.95583, 2); // 1.96

yes, I see. I don't think forena can understand the default numeric format with the , as the decimal indicator. This may have to do with language settings on oracle, or it may be the field is a text field in oracle. If the latter is the case try adding a CAST statement to your column select, like this:

select cast(mycol as numeric(6,2)) as total from...

But my bet is the decimal characters are specified in your database connection, as described here:
http://docs.oracle.com/cd/E11882_01/server.112/e10729/ch3globenv.htm#NLS...

To overcome this in the date format, I am setting the date format to be ISO standard when I connect to oracle. Do you think it would be appropriate to do so for the numeric format as well. This could change the way all decimals look on your report though if I do, so I wan't to be careful here.

Thoughts?

Near line 48 of FrxOracle.inc there is an ALTER SESSION command to set dates. The most straightforward thing to do is to add another to this list. If someone comes up with a use case for this I can always add a setting later, but I'm inclined to not provide the configuration option, since the , based decimal doesn't really work right in Forena. IF there are no objections, I'll proceed in this fashion.

I a bit did not got idea from last message, because now there is a problem, that I am getting comma(,) as decimal separator and therefore the formating does now work right.

Did you mean "does not work right". If so, that's my point. PHP will never cast numbers properly that come out with a "," as a decimal separator, which will give all kinds of problems for casting data in the data typing and formatting features. This is why I suggested that we might make this the normal behavior. If I were to provide it as an option I would want to put in disclaimers that many of the features of forena would break when using this option. (cause they will).

Do you still think we need to provide the option or should it be handled by formatting functions like you are trying to do?

Ok this has been done and commited in the dev branch and will be available in the next release. I haven't had a chance to test it yet (don't have oracle on my mac), but will a bit later at work today. Code is avialable via git for testing.