| Author |
Message |
|
|
Hi Wes,
I have confirmed that this is indeed a bug that still exists in the current codebase. Thank you for reporting it. I hope that we can get it fixed as soon as possible.
|
 |
|
|
Hi eason,
We look forward to seeing your contribution!
Also, I recommend that you sign up for our Developer's Mailing List at http://groups.google.com/group/architect-developers
|
 |
|
|
The Oracle error message (java.sql.SQLException: ORA-00936: missing expression) would suggest the our driver wrapper executed an incomplete SQL statement.
Unfortunately, the error log doesn't indicate what exactly was wrong with the statement, so we will have to do some digging around.
|
 |
|
|
Hello,
This is a known issue and should be fixed in the latest builds.
Original bug report is here:
http://code.google.com/p/power-matchmaker/issues/detail?id=4&can=1
|
 |
|
|
Hi Benjamin,
Thank you for reporting these issues. We will look into them.
|
 |
|
|
Hi everyone,
The DQguru development team has decided to try out using the Google Code Issues database for tracking bugs for the DQguru project. The reasoning for this is that we feel that the Google Code Issues user interface is simpler and friendlier to end users, and will help make it easier for users to report bugs more effectively. The new system is located at http://code.google.com/p/power-matchmaker/issues/list
There is a list of older bugs still in our Bugzilla database. These will remain there for reference, but you will no longer be able to enter new bugs through that interface. Instead, please report bugs in the new system (http://code.google.com/p/power-matchmaker/issues/list). Over time, we may transfer the bug reports from Bugzilla over to the new system.
|
 |
|
|
|
Looks like this is a bug that's being caused by a change made to the code back in early March. This may have also broken some of the other steps.
|
 |
|
|
|
I just uploaded them. Sorry about that! It's nice to know that some people are actually interested in our release candidate source code!
|
 |
|
|
It's more complicated than it could be right now. Currently, you would be required to implement a logic class and a GUI class, and ideally provide an icon (although that could be optional). There is a properties file embedded in the DQguru which maps the logic and gui classes and the icons together, and the DQguru uses this to build the transformer library.
I would be open to the idea of a GUI for managing your 'transformer library'.
|
 |
|
|
The idea of 'composite tranformers' (as I call them) or whatever you'd like to call them has come up before, but we haven't gotten around to implementing it. That said, it's a neat idea, and if we can design the user interface bit of it properly, I think it would be a handy tool for making more complex tranformations.
I'll keep your suggestion in mind when we're doing future planning.
|
 |
|
|
Hey folks,
I was finally able to get the forum search index working again so that older posts can be searched. So you can use the search feature again to find old posts.
|
 |
|
|
The table Demo_DB.JK.Demo_table already exists
It would appear that the table of that name already exists. I would suggest renaming the table to something different.
|
 |
|
|
Hi Benjamin,
Thanks for catching these issues.
It is possible to add your own transformers, but it does require writing some Java code.
If you're interested in learning more on how to write your own transformers, i invite you to join our developer discussion group on Google Groups:
http://groups.google.com/group/matchmaker-developers
|
 |
|
|
Hmm, apparently DQ guru 'thinks' that you've modified the source table in some way since you created the project.
Do you know what OS is your MySQL instance running on?
|
 |
|
|
Hi there,
If you set the log level to 'DEBUG' (There should be a 'Message Level' option with a dropdown box when you're on the Run Match Engine screen. Set it to DEBUG'). You should see some more detailed information in the log panel that appears below the progress bar.
If you have time, you could try copying and pasting that into a text file and then attaching in to a response here. This could give some additional information that could be useful in fixing this issue.
|
 |
|
|