Add text field for logical name in ColumnEditPanel and add variable to store the value. Also made some test cases for this new property.

git-svn-id: http://power-architect.googlecode.com/svn/trunk@2972 ef18fcdb-8a34-0410-ae7e-c1cd3e483e87
Used name of SQLObject as the field for logical name instead of creating a new variable logicalName. Modified test cases and editing panels for tables and columns. This is still in its initial stage and so now it won't work for forward  and reverse engineering.

git-svn-id: http://power-architect.googlecode.com/svn/trunk@2973 ef18fcdb-8a34-0410-ae7e-c1cd3e483e87
Changed method and variable names from 'technical' and 'alias'
names to 'physical' and 'logical' names.
 
The project now remembers its logical or physical name display settings. New projects have it set by default to display the logical names. The playpen updates the table panes whenever the user changes his name display settings.

git-svn-id: http://power-architect.googlecode.com/svn/trunk@2974 ef18fcdb-8a34-0410-ae7e-c1cd3e483e87
1.Now allows the user to touch the physical name of SQLColumn and SQLTable. Physical name will not be generated or corrected when forward engineer if user has set one but will pop up a warning if it's not valid for the specific database. So far the user has to set the logical name for a column or table, we can generate the physical name for them like before if physical name is blank. 

2.Also modified SQLRelationship and SQLIndex to use physical name if it's not empty instead of logical name anymore.

3.Added some test cases for physical name and changed some test cases for SQLColumnSQLRelationship and TableEditPanel.

This is a fix for bug 1784. Notice that the user will lose their logical names if they forward and then reverse engineer. However, they are supposed to save the project to save their logical names. 
Michelle is working on reporting formats, which is the only thing left for this bug fix.

git-svn-id: http://power-architect.googlecode.com/svn/trunk@2975 ef18fcdb-8a34-0410-ae7e-c1cd3e483e87
Fix for "relationship lines appear to vanish when selected." (This issue was reported on the forum by bronius).

Now we use SQL Power Orange for selected relations that can't be darkened. We also changed the column highlight to match, so it's now more obvious what the column highlight means in this context.

With additional suggestions from Giulio, we now also double the line thickness when a relationship is selected, since colour alone can be ambiguous.

git-svn-id: http://power-architect.googlecode.com/svn/trunk@2976 ef18fcdb-8a34-0410-ae7e-c1cd3e483e87
This commit is the copy, cut, and paste feature for tables and columns.
Pasting is allowed between sessions and even contexts. Copying and
pasting is allowed in the playpen and columns can also be copied by
dragging when holding down the correct modifier.

git-svn-id: http://power-architect.googlecode.com/svn/trunk@2977 ef18fcdb-8a34-0410-ae7e-c1cd3e483e87
Fixed a test suite failure caused by the red->orange change. The test now no longer uses a hardcoded expected colour for column highlight.

Also changed to the BREWER19 colour scheme for relationship colour suggestion and cleaned up some of the code that sets it up (it was using background colours before, which were too light for the thin relationship lines to be visible especially when zoomed out).

git-svn-id: http://power-architect.googlecode.com/svn/trunk@2978 ef18fcdb-8a34-0410-ae7e-c1cd3e483e87
Fixed bug 1787

git-svn-id: http://power-architect.googlecode.com/svn/trunk@2979 ef18fcdb-8a34-0410-ae7e-c1cd3e483e87
Undid some changes to make moving columns involved with relationships
work again. 
Also added the ability to paste in text into the play pen and have
tables be created by the names pasted in. Columns can also be
created by pasting in text.

git-svn-id: http://power-architect.googlecode.com/svn/trunk@2980 ef18fcdb-8a34-0410-ae7e-c1cd3e483e87
Added an ExportHTMLReportAction which generates a report in html off of the content in the playpen using a specific stylesheet. 
The Action can be found under the File menu.
Made some changes to the architect2html.xslt stylesheet provided to us courtesy of forum users bronius and castorp and added it to the folder xsltStylesheets in the src package. 

git-svn-id: http://power-architect.googlecode.com/svn/trunk@2981 ef18fcdb-8a34-0410-ae7e-c1cd3e483e87
Fixed the bug that happened in the architect user group meeting which the sequence name of the column becomes very long after forward engineering. Now the sequence name takes the physical name of the table instead of the logical name.  (For reverse engineer reason, now the physical name of the table sets to be the same as the logical name in the constructor of the SQLTable.)

git-svn-id: http://power-architect.googlecode.com/svn/trunk@2982 ef18fcdb-8a34-0410-ae7e-c1cd3e483e87
Fixed the bug 1483 which requires relationship label to be added. Now user can toggle to display or hide relationship label from project settings and the label is designed to be clockwise readable. This commit doesn't support dragging labels to different places, but I think that feature will be accomplished by Architect User Created Label function in the future. I suppose the bug 1483 is resolved.

git-svn-id: http://power-architect.googlecode.com/svn/trunk@2983 ef18fcdb-8a34-0410-ae7e-c1cd3e483e87
Updated for the changes to the library. The SQLQueryUIComponents now
need a DatabaseMapping which is implemented by the session to give
the Universal SQL Access tool SQLDatabase objects to help protect
against connection leaks.

git-svn-id: http://power-architect.googlecode.com/svn/trunk@2984 ef18fcdb-8a34-0410-ae7e-c1cd3e483e87
Fixed some mistakes of relationshipLabel and now support user defined relationship label. So far labels can only be edited through relationshipEditPanel and cannot be dragged. But it's easier now to implement those two more features.

git-svn-id: http://power-architect.googlecode.com/svn/trunk@2985 ef18fcdb-8a34-0410-ae7e-c1cd3e483e87
Added the rethrow boolean to the LoadSQLObjectAttributes which was 
added to the library. Loading does not need to rethrow saved exceptions.

git-svn-id: http://power-architect.googlecode.com/svn/trunk@2986 ef18fcdb-8a34-0410-ae7e-c1cd3e483e87
I'm about to remove the physicalPrimaryKeyName property from SQLTable, and these changes accommodate that.

As a nice side effect, I found and fixed bugs in adding and dropping keys in MySQL, PostgreSQL, and SQL Server (some syntax errors, and some use of the logical key name where physical should have been used)

git-svn-id: http://power-architect.googlecode.com/svn/trunk@2987 ef18fcdb-8a34-0410-ae7e-c1cd3e483e87
Tweak to the fix in r2979: now table name matching is done case insensitively (as always), and the target table names are quoted (as fixed in r2979), BUT now the actual target table names are being used rather than the source table names. Up until r2979, there was no practical difference between source and target names; now that they're quoted, there is.

git-svn-id: http://power-architect.googlecode.com/svn/trunk@2988 ef18fcdb-8a34-0410-ae7e-c1cd3e483e87
Delete some useless code for relationship label.

git-svn-id: http://power-architect.googlecode.com/svn/trunk@2989 ef18fcdb-8a34-0410-ae7e-c1cd3e483e87
The xslt stylesheets folder was not being built into the build directory. This is a fix for it.

git-svn-id: http://power-architect.googlecode.com/svn/trunk@2990 ef18fcdb-8a34-0410-ae7e-c1cd3e483e87
Fix for a forum bug report: columns marked as BIGINT were not being forward engineered as BIGINT in PostgreSQL, even though it supports that type.

git-svn-id: http://power-architect.googlecode.com/svn/trunk@2991 ef18fcdb-8a34-0410-ae7e-c1cd3e483e87