<!-- 
RSS generated by JIRA (5.2.7#850-sha1:b2af0c8dc8537b36121c6a579fabbdf79fc919e5) at Wed Jun 19 10:29:21 UTC 2013

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
For example:
http://www.doctrine-project.org/jira/si/jira.issueviews:issue-xml/DMIG-31/DMIG-31.xml?field=key&field=summary
-->
<rss version="0.92" >
<channel>
    <title>Doctrine Project</title>
    <link>http://www.doctrine-project.org/jira</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>5.2.7</version>
        <build-number>850</build-number>
        <build-date>21-02-2013</build-date>
    </build-info>

<item>
            <title>[DMIG-31] $table-&gt;renameColumn() actually drops the column</title>
                <link>http://www.doctrine-project.org/jira/browse/DMIG-31</link>
                <project id="10041" key="DMIG">Doctrine Migrations</project>
                        <description>&lt;p&gt;Tried to use renameColumn() into one of my migration scripts and it dropped the table.&lt;/p&gt;

&lt;p&gt;The code does not seem okay as well:&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;namespace Doctrine\DBAL\Schema;
..
class Table extends AbstractAsset
{
..
  /**
    * Rename Column
    *
    * @param string $oldColumnName
    * @param string $newColumnName
    * @return Table
    */
public function renameColumn($oldColumnName, $newColumnName)
{
    $column = $this-&amp;gt;getColumn($oldColumnName);
    $this-&amp;gt;dropColumn($oldColumnName);

    $column-&amp;gt;_setName($newColumnName);
    return $this;
}
..
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</description>
                <environment>symfony 2.0.7</environment>
            <key id="13297">DMIG-31</key>
            <summary>$table-&gt;renameColumn() actually drops the column</summary>
                <type id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="2" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/critical.png">Critical</priority>
                    <status id="5" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/resolved.png">Resolved</status>
                    <resolution id="3">Duplicate</resolution>
                                <assignee username="beberlei">Benjamin Eberlei</assignee>
                                <reporter username="nikola.petkanski">Nikola Petkanski</reporter>
                        <labels>
                    </labels>
                <created>Fri, 23 Dec 2011 08:48:05 +0000</created>
                <updated>Tue, 19 Jun 2012 13:23:07 +0000</updated>
                    <resolved>Mon, 4 Jun 2012 07:26:47 +0000</resolved>
                                                                    <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                        <comments>
                    <comment id="17373" author="veonik" created="Mon, 6 Feb 2012 22:32:01 +0000"  >&lt;p&gt;Doctrine\DBAL\Schema\Table is actually not a part of Doctrine Migrations, rather just the Database Abstraction Layer project. Recommend this gets sorted as such.&lt;/p&gt;</comment>
                    <comment id="18036" author="dbu" created="Mon, 4 Jun 2012 07:24:03 +0000"  >&lt;p&gt;this is a duplicate of &lt;a href=&quot;http://www.doctrine-project.org/jira/browse/DMIG-22&quot; title=&quot;$table-&amp;gt;renameColumn doesn&amp;#39;t work&quot;&gt;&lt;del&gt;DMIG-22&lt;/del&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;any chances of getting the issue fixed?&lt;/p&gt;</comment>
                    <comment id="18037" author="beberlei" created="Mon, 4 Jun 2012 07:26:38 +0000"  >&lt;p&gt;From the internals this is really complicated. I will delete the method instead.&lt;/p&gt;</comment>
                    <comment id="18098" author="gomox" created="Tue, 19 Jun 2012 13:23:07 +0000"  >&lt;p&gt;Does this mean Doctrine Migrations won&apos;t support renaming columns? I&apos;m sorry but the alternative of not supporting it at all doesn&apos;t really work. It&apos;s a basic operation for DB schema changes, which are the whole point of migrations. What exactly is the proble? I have seen the algorithms for inferring that a column or table should be renamed and they are pretty simplistic. Maybe the solution is adding some sort of hinting to the renameX operations so that there is metadata inside the Table Schemas saying what the original columns or tables were. Thoughts?&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>
</channel>
</rss>