-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
$P!{name} Parameters #46
Comments
Can anyone pass these parameters? |
Hi, |
I understand, in making filters based on individual parameters, but that makes the sql assembly much more complex... something that in the application there are many filters and makes them dynamic, so when passing the formulated parameter already as a kind of p_where, it makes it easier the process a lot, and as I said that way jasperreport native jasper api supports... and it makes it much easier to use this type of parameter, with that I pass a completely customized p_where. |
ok,i think to support it, |
step a sql ex: final result just an example, that is, I pass a sql script that filters the records, so I can pass a very complex sql with several filters... |
try this ($P{p_where}) without "!" |
Without ! seems to solve yes... because I did a debug printing the generated sql and now yes it is generating correctly... but I have other problems in the report anything I open another post. Here's just one suggestion that I inform you is the possibility of changing the patch directory of ini config files for database connection because in my case, I already have this file pattern because I also use PDO so I wanted to use the same files... |
About PDO, i use one solution, runs perfect for me, you can change on line Line 7 in ee16f92
and implement a copy of Transaction Class, but taking connection parameters in your config file. About slow reports, i think that much objects can make report slower, i have in my systems reports what generate mor then 60 pages in less of 6 seconds, containing 3 level sub reports with querys, passing parameters end receiving totalizers. |
JasperPHP\ado\TTransaction::open("dev"); when I refer to changing the patch, I refer to the possibility, for example, of changing the directory where the dev.ini file is, or even some parameter that says that a complete patch of the file is being passed, because as I said, I already have files in another folder ini config files and didn't want to be duplicating the config files |
Add the solution JasperPHP/src/ado/TConnection.php Line 30 in c1a338d
pass full path of file including extension |
yes.. |
how to work with this type of parameter, used for example to pass sql statements, I know it may be a failure for sql injector but it will not be used for parameter edited by the user and in jasperReporta it works normally. I wanted to know how to adopt in your api.
select * from pessoa where ($P!{p_where})
??
The text was updated successfully, but these errors were encountered: