Error importing view to Firebird
8 January, 2013
Hello guys!!!
We have a problem importing views to Firebird. I will explain how is my system and how I have imported the views.
My system is:
. Yellowfin 6.2
. Java Version 1.7.0_4
. Operating System Windows 7
. Datawarehouse used: Firebird 1.5 (it's a requirement for the customer)
. Jdbc used: JayBird-2.0.1JDK_1.5 (in the release notes says that Firebird 1.5 is supported)
. Database for metadata mysql 5.x
The process that I have done to import is:
. A)From source we export all the items
. B)In the target, we have created a data source with Firebird
. C)We start the process to import the views and reports.
- Import all the elements excep the data source, we use the data source created in the second step.
. D)The process has finished correctly.
. E)Then We go to edit the view imported in previous steps and we try to drag a field in the step 2 of Edit View Wizard and appears the error. (See first image)
. F)Now we try to modify the second view imported, I go to the step 2 of Edit View Wizard and I can't do nothing (see second image)
I have attached all the logs that show Exception
Note1: To create a connection in Firebird YOU NEED TO USE because if you use only it doesn't work.
Note2: If in the target Pc, I import all the elements (also the data source) then the reports are not working. It gives me an sql error. If I create a data source in the target Pc, and I import all the elements (no data source element) then the reports are working correctly.
In a private mail I have send you the xml file to import and the database.
We have a problem importing views to Firebird. I will explain how is my system and how I have imported the views.
My system is:
. Yellowfin 6.2
. Java Version 1.7.0_4
. Operating System Windows 7
. Datawarehouse used: Firebird 1.5 (it's a requirement for the customer)
. Jdbc used: JayBird-2.0.1JDK_1.5 (in the release notes says that Firebird 1.5 is supported)
. Database for metadata mysql 5.x
The process that I have done to import is:
. A)From source we export all the items
. B)In the target, we have created a data source with Firebird
. C)We start the process to import the views and reports.
- Import all the elements excep the data source, we use the data source created in the second step.
. D)The process has finished correctly.
. E)Then We go to edit the view imported in previous steps and we try to drag a field in the step 2 of Edit View Wizard and appears the error. (See first image)
. F)Now we try to modify the second view imported, I go to the step 2 of Edit View Wizard and I can't do nothing (see second image)
I have attached all the logs that show Exception
Note1: To create a connection in Firebird YOU NEED TO USE because if you use only it doesn't work.
Note2: If in the target Pc, I import all the elements (also the data source) then the reports are not working. It gives me an sql error. If I create a data source in the target Pc, and I import all the elements (no data source element) then the reports are working correctly.
In a private mail I have send you the xml file to import and the database.
Hi there Jordi!
thanks for all the attachments and the descriptive reproduction steps, it certainly makes things easier. Yes we were able to reproduce the importing error over here.
I have raised a product defect (task ID = 123949) for this, unfortunately the developer who looks after this sort of problem is away on vacation at the moment and he is returning to work on the 21st of January. So I can't promise any investigation of the issue until then, and even when he is back there mightn't be enough time left in the month to fix it for the January build, so it's most likely to be for the February build.
Apologies for the inconvenience.
Regards,
Dave
thanks for all the attachments and the descriptive reproduction steps, it certainly makes things easier. Yes we were able to reproduce the importing error over here.
I have raised a product defect (task ID = 123949) for this, unfortunately the developer who looks after this sort of problem is away on vacation at the moment and he is returning to work on the 21st of January. So I can't promise any investigation of the issue until then, and even when he is back there mightn't be enough time left in the month to fix it for the January build, so it's most likely to be for the February build.
Apologies for the inconvenience.
Regards,
Dave
Thanks David