<!-- 
RSS generated by JIRA (5.2.7#850-sha1:b2af0c8dc8537b36121c6a579fabbdf79fc919e5) at Sat May 25 18:14:07 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/DBAL-75/DBAL-75.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>[DBAL-75] SchemaTool-&gt;getDropSchemaSql ignores schema name</title>
                <link>http://www.doctrine-project.org/jira/browse/DBAL-75</link>
                <project id="10040" key="DBAL">Doctrine DBAL</project>
                        <description>&lt;p&gt;When including the schema name as part of the table name, i.e.&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;/**
 * @Entity
 * @Table(name=&lt;span class=&quot;code-quote&quot;&gt;&quot;ayso.players&quot;&lt;/span&gt;)
 */
class PlayerItem
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;SchemaTool-&amp;gt;getDropSchemaSql returns &quot;DROP TABLE players&quot; instead of &quot;DROP TABLE ayso.players&quot;&lt;/p&gt;

&lt;p&gt;Furthermore, SchemaTool-&amp;gt;getUpdateSchemaSql() always returns CREATE TABLE ayso.players followed by DROP TABLE players.  It thinks there are two different tables.&lt;/p&gt;

&lt;p&gt;Also, the online document still indicates that @Table accepts &apos;schema&apos; as an attribute.&lt;/p&gt;</description>
                <environment>NA</environment>
            <key id="12143">DBAL-75</key>
            <summary>SchemaTool-&gt;getDropSchemaSql ignores schema name</summary>
                <type id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/minor.png">Minor</priority>
                    <status id="5" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/resolved.png">Resolved</status>
                    <resolution id="1">Fixed</resolution>
                                <assignee username="beberlei">Benjamin Eberlei</assignee>
                                <reporter username="cerad">Art Hundiak</reporter>
                        <labels>
                    </labels>
                <created>Tue, 23 Nov 2010 07:39:05 +0000</created>
                <updated>Sun, 12 Dec 2010 08:39:28 +0000</updated>
                    <resolved>Sun, 12 Dec 2010 08:39:28 +0000</resolved>
                            <version>2.0-RC4</version>
                                <fixVersion>2.0-RC5</fixVersion>
                                <component>Schema Managers</component>
                        <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                        <comments>
                    <comment id="14961" author="beberlei" created="Sun, 12 Dec 2010 07:24:38 +0000"  >&lt;p&gt;Moved to DBAL, its a DBAL issue.&lt;/p&gt;</comment>
                    <comment id="14962" author="beberlei" created="Sun, 12 Dec 2010 08:39:28 +0000"  >&lt;p&gt;Fixed in DBAL master, will be included for RC5. Then linked against ORM RC2&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>
</channel>
</rss>