Home » Archived » BIRT » input parametes and some suggestions
| input parametes and some suggestions [message #22358] |
Wed, 23 March 2005 20:26  |
 Sven Boden
Messages: 15
Registered: July 2009 |
Junior Member |
|
|
Hi,
I've been testing BIRT a bit, great designer, looking very good in general.
If it can help, a test case for the "input parameter problem":
1) I follow the tutorial until the end.
2) Go in Data Explorer, expand Data Sets and left double click on Customers
3) In the Query tab add "where custid = ?" on line 3
4) Click on ok and you will get a message as
"org.eclipse.birt.data.engine.core.DataException occurred Error
Code:DATA_EXCEPTION_odaconsumer.CannotExecuteStatement Error
Code:DATA_EXCEPTION_odaconsumer.CannotExecuteStatement Error Message:Cannot
execute the statement. A JDBC Exception occured: [Microsoft][ODBC Microsoft
Access Driver]COUNT field incorrect
[Microsoft][ODBC Microsoft Access Driver]COUNT field incorrect".
I don't have an idea why the designer would try to execute the query upon
exiting
Then
1) Go in Data Explorer, expand Data Sets and left double click on Customers
(not that the new where clause is in there)
2) Go to the "Input Parameters" tab
3) Left click once on the first line in the Name cell, and enter custid
4) click in another empty cell on another line (a new empty parameter line
will appear). Now press the Ok button => this does not work
5) Now click on "Filters", and press the "ok" button => Does not work
6) Click on "Output Columns", and press the "ok" button there => The dialog
closes and the input parameter is saved.
This is something to do with validation which only work on the current tab
or so.
Then
1) Go in Data Explorer, expand Data Sets and left double click on Customers
(not that the new where clause is in there)
2) Go to the "Preview Results" and the following message appears
"java.lang.IllegalArgumentException occurred
Parameter position cannot be less than 1."
--------------------------------------------------
Other Suggestions:
If I follow the tutorial and choose all columns from table customers I get
something as "SELECT * FROM [customers]" as query in the dataset, I would
suggest to expand this to the actual named columns instead of "*"... one day
someone is going to add a column to a database table, ...
If you right click on a report in "Navigator" and select properties the Text
file encondig defaults to CP1252, is there a reason for this? Most tools
would default to 8859-1, but I would see not even see a problem in
defaulting it to UTF-8 e.g.
When using the "Preview button in the toolbar" to view the tutorial example
the Page number at the bottom of the pages is not filled in. (this is
probably what's meant in the gray box on the tutorial page right below that
piece).
For later when non Actuate developers start developing their own extensions
I would suggest to do some kind of "Actuate approved extension" label for
important components. E.g. if some developer would write some "bad"
extension everyone could use it, but it would not be advised.
Regards,
Sven
|
|
|
| Re: input parametes and some suggestions [message #22471 is a reply to message #22358] |
Wed, 23 March 2005 23:23  |
Paul Rogers
Messages: 152
Registered: July 2009 |
Senior Member |
|
|
Sven,
The current build has known problems with parameters in SQL statements. The
team is working on the problem. Sorry for the inconvenience.
- Paul
"Sven Boden" <svenboden@hotmail.com> wrote in message
news:d1so80$9de$1@news.eclipse.org...
> Hi,
>
> I've been testing BIRT a bit, great designer, looking very good in
> general.
>
> If it can help, a test case for the "input parameter problem":
> 1) I follow the tutorial until the end.
> 2) Go in Data Explorer, expand Data Sets and left double click on
> Customers
> 3) In the Query tab add "where custid = ?" on line 3
> 4) Click on ok and you will get a message as
> "org.eclipse.birt.data.engine.core.DataException occurred Error
> Code:DATA_EXCEPTION_odaconsumer.CannotExecuteStatement Error
> Code:DATA_EXCEPTION_odaconsumer.CannotExecuteStatement Error
> Message:Cannot
> execute the statement. A JDBC Exception occured: [Microsoft][ODBC
> Microsoft
> Access Driver]COUNT field incorrect
> [Microsoft][ODBC Microsoft Access Driver]COUNT field incorrect".
> I don't have an idea why the designer would try to execute the query upon
> exiting
>
> Then
> 1) Go in Data Explorer, expand Data Sets and left double click on
> Customers
> (not that the new where clause is in there)
> 2) Go to the "Input Parameters" tab
> 3) Left click once on the first line in the Name cell, and enter custid
> 4) click in another empty cell on another line (a new empty parameter line
> will appear). Now press the Ok button => this does not work
> 5) Now click on "Filters", and press the "ok" button => Does not work
> 6) Click on "Output Columns", and press the "ok" button there => The
> dialog
> closes and the input parameter is saved.
> This is something to do with validation which only work on the current tab
> or so.
>
> Then
> 1) Go in Data Explorer, expand Data Sets and left double click on
> Customers
> (not that the new where clause is in there)
> 2) Go to the "Preview Results" and the following message appears
> "java.lang.IllegalArgumentException occurred
> Parameter position cannot be less than 1."
>
> --------------------------------------------------
>
> Other Suggestions:
> If I follow the tutorial and choose all columns from table customers I get
> something as "SELECT * FROM [customers]" as query in the dataset, I would
> suggest to expand this to the actual named columns instead of "*"... one
> day
> someone is going to add a column to a database table, ...
>
> If you right click on a report in "Navigator" and select properties the
> Text
> file encondig defaults to CP1252, is there a reason for this? Most tools
> would default to 8859-1, but I would see not even see a problem in
> defaulting it to UTF-8 e.g.
>
> When using the "Preview button in the toolbar" to view the tutorial
> example
> the Page number at the bottom of the pages is not filled in. (this is
> probably what's meant in the gray box on the tutorial page right below
> that
> piece).
>
> For later when non Actuate developers start developing their own
> extensions
> I would suggest to do some kind of "Actuate approved extension" label for
> important components. E.g. if some developer would write some "bad"
> extension everyone could use it, but it would not be advised.
>
> Regards,
> Sven
>
>
|
|
|
| Re: input parametes and some suggestions [message #22644 is a reply to message #22471] |
Thu, 24 March 2005 21:11 |
Sven Boden
Messages: 15
Registered: July 2009 |
Junior Member |
|
|
Abolutely no problem, I'll see whether I can get do some debugging myself
for the small problems I've found. The testcases where just in case someone
wants a consistent way of reproducing the input parameter problem.
Sven
"Paul Rogers" <progers@actuate.com> wrote in message
news:d1t2jr$lon$1@news.eclipse.org...
> Sven,
>
> The current build has known problems with parameters in SQL statements.
The
> team is working on the problem. Sorry for the inconvenience.
>
> - Paul
>
> "Sven Boden" <svenboden@hotmail.com> wrote in message
> news:d1so80$9de$1@news.eclipse.org...
> > Hi,
> >
> > I've been testing BIRT a bit, great designer, looking very good in
> > general.
> >
> > If it can help, a test case for the "input parameter problem":
> > 1) I follow the tutorial until the end.
> > 2) Go in Data Explorer, expand Data Sets and left double click on
> > Customers
> > 3) In the Query tab add "where custid = ?" on line 3
> > 4) Click on ok and you will get a message as
> > "org.eclipse.birt.data.engine.core.DataException occurred Error
> > Code:DATA_EXCEPTION_odaconsumer.CannotExecuteStatement Error
> > Code:DATA_EXCEPTION_odaconsumer.CannotExecuteStatement Error
> > Message:Cannot
> > execute the statement. A JDBC Exception occured: [Microsoft][ODBC
> > Microsoft
> > Access Driver]COUNT field incorrect
> > [Microsoft][ODBC Microsoft Access Driver]COUNT field incorrect".
> > I don't have an idea why the designer would try to execute the query
upon
> > exiting
> >
> > Then
> > 1) Go in Data Explorer, expand Data Sets and left double click on
> > Customers
> > (not that the new where clause is in there)
> > 2) Go to the "Input Parameters" tab
> > 3) Left click once on the first line in the Name cell, and enter custid
> > 4) click in another empty cell on another line (a new empty parameter
line
> > will appear). Now press the Ok button => this does not work
> > 5) Now click on "Filters", and press the "ok" button => Does not work
> > 6) Click on "Output Columns", and press the "ok" button there => The
> > dialog
> > closes and the input parameter is saved.
> > This is something to do with validation which only work on the current
tab
> > or so.
> >
> > Then
> > 1) Go in Data Explorer, expand Data Sets and left double click on
> > Customers
> > (not that the new where clause is in there)
> > 2) Go to the "Preview Results" and the following message appears
> > "java.lang.IllegalArgumentException occurred
> > Parameter position cannot be less than 1."
> >
> > --------------------------------------------------
> >
> > Other Suggestions:
> > If I follow the tutorial and choose all columns from table customers I
get
> > something as "SELECT * FROM [customers]" as query in the dataset, I
would
> > suggest to expand this to the actual named columns instead of "*"... one
> > day
> > someone is going to add a column to a database table, ...
> >
> > If you right click on a report in "Navigator" and select properties the
> > Text
> > file encondig defaults to CP1252, is there a reason for this? Most tools
> > would default to 8859-1, but I would see not even see a problem in
> > defaulting it to UTF-8 e.g.
> >
> > When using the "Preview button in the toolbar" to view the tutorial
> > example
> > the Page number at the bottom of the pages is not filled in. (this is
> > probably what's meant in the gray box on the tutorial page right below
> > that
> > piece).
> >
> > For later when non Actuate developers start developing their own
> > extensions
> > I would suggest to do some kind of "Actuate approved extension" label
for
> > important components. E.g. if some developer would write some "bad"
> > extension everyone could use it, but it would not be advised.
> >
> > Regards,
> > Sven
> >
> >
>
>
|
|
|
Goto Forum:
Current Time: Fri Dec 27 01:30:28 GMT 2024
Powered by FUDForum. Page generated in 0.03473 seconds |
] 
Search
Help
Register
Login
Home
