SQL Power Software Forum

Hey MatchMaker Creators,

Apparently, currently with the MatchMaker, if the user selects AutoMatch, the Master record is chosen randomly. Maybe a user should be able to set certain criteria to dictate which record should be the master record.
i.e.) the most recent create date, or update date, or the one with the least fields of null data.

I know I would use that feature.

OS: Windows
Version of MatchMaker: 0.9.3-alpha

Issue:
I created the MatchMaker results table outside of MatchMaker. Then I tried to create a new project using that results table. After filling in the required fields for the project and then clicking save, the SQL statement to create the output table appears. If I close this window a second window opens indicating that the project has not been saved. I would expect that the project would save because the output table already exists.

Suggestion:
Have the ability to match on one schema and be able to save the output/result tables on another schema.

The issue that initiated this suggestion:
Using Oracle.

Connected to a remote repository on schema Y. I tried to create a de-duping project. The tables that I wanted to do the matching on were on one schema called 'X'.

In the "Data Source:" field, I chose the connection that points to schema X.
Source Table "Schema:" I chose schema X, and the table from that schema that I wanted to do the matching on.
For the Output Table "Schema:" I selected schema Y, and allowed the table name to be defaulted.

When I clicked on the save button, Create Result Table window appears. There are 2 SQL statements;
1. Create Table
2. Create Unique index

When I click on Execute an error message appears:
"The error was: ORA-01031 insufficient privileges"

If I use another tool to create the table logged in as a user for the Y schema I can execute the 2 SQL statements.

Thanks, that solved the issue.

The sequence of events before the error occurred:
Connected to an Oracle repository.
Trying to create a New Project folder. Right clicked on Current Projects to create a new folder.
Typed in a Folder name and description.
Clicked on the save button.

Caught Background Exception Error appeared.
Exception Type: org.hibernate.PropertyAccessException

org.hibernate.PropertyAccessException: Exception occurred inside getter of ca.sqlpower.matchmaker.Project.sourceTableIndex
at org.hibernate.property.BasicPropertyAccessor$BasicGetter.get(BasicPropertyAccessor.java:14

at org.hibernate.tuple.entity.AbstractEntityTuplizer.getPropertyValues(AbstractEntityTuplizer.java:256)
at org.hibernate.tuple.entity.PojoEntityTuplizer.getPropertyValues(PojoEntityTuplizer.java:209)
at org.hibernate.persister.entity.AbstractEntityPersister.getPropertyValues(AbstractEntityPersister.java:3509)
at org.hibernate.event.def.DefaultFlushEntityEventListener.getValues(DefaultFlushEntityEventListener.java:160)
at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:113)
at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:195)
at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76)
at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:26)
at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000)
at ca.sqlpower.matchmaker.dao.hibernate.AbstractMatchMakerDAOHibernate.save(Unknown Source)
at ca.sqlpower.matchmaker.dao.hibernate.AbstractMatchMakerDAOHibernate.save(Unknown Source)
at ca.sqlpower.matchmaker.FolderParent.addNewChild(Unknown Source)
at ca.sqlpower.matchmaker.swingui.FolderEditor.applyChanges(Unknown Source)
at ca.sqlpower.matchmaker.swingui.FolderEditor$2.actionPerformed(Unknown Source)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at javax.swing.JComponent.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.hibernate.property.BasicPropertyAccessor$BasicGetter.get(BasicPropertyAccessor.java:145)
... 39 more
Caused by: java.lang.IllegalArgumentException: Error: No database connection named hotblack - marketing test please create a database connection named hotblack - marketing test and try again.
at ca.sqlpower.matchmaker.CachableTable.getSPDataSource(Unknown Source)
at ca.sqlpower.matchmaker.CachableTable.getSourceTable(Unknown Source)
at ca.sqlpower.matchmaker.TableIndex.getTableIndex(Unknown Source)
at ca.sqlpower.matchmaker.Project.getSourceTableIndex(Unknown Source)
... 44 more

Please help.

When creating a table that is a copy of a table in an Oracle database.
There is an issue when, a column type timestamp(6), in the original table is copied into the playpen to be forward engineered in another schema. The column type that is created in the new schema is a varchar.

Hi,

The Forward Engineering is awesome. I would like that when "Conflicting Objects Found" window comes up the user has the option to chose which objects to drop. When people are working in groups, they may not want to drop tables that are the responsibility of someone else on the team.

This idea could also be applied to the compare database as well. Only making the changes that the user is sure should be made.

javascript:emoticon('

');
javascript:emoticon('

');

Hi,

I totally agree with the suggestion on the amount of zoom.

When using the find function of Power Architect,
suggestion: when a table is found and the user choses to view it and clicks on the Show in Playpen option the playpen should zoom into the table that was chosen.

After creating a new connection. It is not listed in the menu obtained from the tool bar as an option to be added until Power Architect is restarted.

Note: it does appear in the menu obtained from the right click menu.

Provide an option for the result columns in the results to either equate null to null or to not equate them to each other.

Situation: Running MatchMaker on a de-duping project. One munge process that uses the translate word transformation. The result table already contains 2mil rows.

Error - Java Heap Size error.

Running the munge process again, having deleted all rows from the results table there are no issues.

This may be difficult for me to explain. But here goes...

If creating a munge process, and there is an existing link from the table to the munge results. When I drag another munge process over the link, there should be an option to place that munge process in that flow.

Jonathan,

I love the idea of placing the munge processes in the order of precedence.
It would be easier for the user to keep track of when there are multiple numbers of munge processes (when pecking order does matter).

Visual representation I think is the best idea.

When defining Munge processes. Instead of setting a priority, I suggest setting a % of Match. To me its more intuitive.

Just a suggestion.