<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/dbexpressplus/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/dbexpressplus/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Thu, 13 Nov 2003 23:17:05 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/dbexpressplus/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>No primary key on table</title><link>https://sourceforge.net/p/dbexpressplus/feature-requests/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Nice work you guys have done here. &lt;/p&gt;
&lt;p&gt;I was just trying out the TSQLDataPump component and&lt;br /&gt;
found that it has what I would consider a bug.&lt;/p&gt;
&lt;p&gt;I have all my tables with no primary key but they all&lt;br /&gt;
have a separate unique index. I like to do it this way&lt;br /&gt;
because I can drop, recreate, or rebuild the indexes&lt;br /&gt;
when I want. The component raises an exception because&lt;br /&gt;
no primary keys are found.&lt;/p&gt;
&lt;p&gt;I would think you would want to check for any indexes&lt;br /&gt;
that are unique and use those (includes primary keys).&lt;/p&gt;
&lt;p&gt;-Mark E.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mark Ericksen</dc:creator><pubDate>Thu, 13 Nov 2003 23:17:05 -0000</pubDate><guid>https://sourceforge.netc0f32b53b8d764c166980f505b30777de079cfc4</guid></item></channel></rss>