This repository has been archived by the owner on Nov 9, 2017. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -111,9 +111,9 @@ | |
| </changeSet> | ||
|
|
||
| <changeSet author="aeng@redhat.com" id="7"> | ||
| <validCheckSum>1484b636bf20f8a55f257622fc9f3cd</validCheckSum> | ||
| <comment>Alter glossary entry table - remove srcTermId/add srcLocaleId/add sourceRef</comment> | ||
| <dropForeignKeyConstraint baseTableName="HGlossaryEntry" constraintName="UKglossaryEntry_glossaryTerm" /> | ||
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong. 
alex-sl-eng
via email
Member
|
||
| <dropColumn tableName="HGlossaryEntry" columnName="srcTermId" /> | ||
|
|
||
| <addColumn tableName="HGlossaryEntry"> | ||
|
|
@@ -131,7 +131,6 @@ | |
| </addColumn> | ||
| </changeSet> | ||
|
|
||
| <changeSet author="aeng@redhat.com" id="8"> | ||
| <comment>Alter glossary tables - remove sourceRef/add auto increment</comment> | ||
|
|
||
|
|
@@ -147,6 +146,7 @@ | |
| <dropForeignKeyConstraint baseTableName="HTermComment" constraintName="UKtermComment_glossaryTerm" /> | ||
| </changeSet> | ||
|
|
||
|
|
||
|
|
||
|
|
||
| </databaseChangeLog> | ||
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes.
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
2 comments
on commit 61affe8
There was a problem hiding this comment.
Why are all these PNGs being renamed in a commit named "fix on changeset 1.5 - 7 for h2 db"?
There was a problem hiding this comment.
My mistake. Eclipse must have put "add" command when i move the package.
Regards,
Alex Eng, Senior Software Engineer
Engineering - Internationalisation
Red Hat, Inc.
…----- Original Message -----
From: "seanf" reply@reply.github.com
To: aeng@redhat.com
Sent: Friday, 2 September, 2011 4:50:31 PM
Subject: Re: [zanata] fix on changeset 1.5 - 7 for h2 db (61affe8)
Why are all these PNGs being renamed in a commit named "fix on changeset 1.5 - 7 for h2 db"?
##
Reply to this email directly or view it on GitHub:
61affe8#commitcomment-565516
What happened to breaking this out into a separate commit which runs only on mysql? Do we still need to drop the unique constraint?