<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: App Review: SQLEditor</title>
	<atom:link href="http://blog.blakeperdue.com/2008/11/16/app-review-sqleditor/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.blakeperdue.com/2008/11/16/app-review-sqleditor/</link>
	<description>Web reviews, app reviews, and technology and startup commentary</description>
	<lastBuildDate>Thu, 06 May 2010 12:29:20 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Matthew Quinlan</title>
		<link>http://blog.blakeperdue.com/2008/11/16/app-review-sqleditor/comment-page-1/#comment-2297</link>
		<dc:creator>Matthew Quinlan</dc:creator>
		<pubDate>Tue, 21 Apr 2009 15:23:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.blakeperdue.com/?p=443#comment-2297</guid>
		<description>This type of tool is also incredibly valuable for LEARNING about data modeling.  While I knew the basics from books, it was really ER-win (the grand-daddy of the data modeling space) that taught me the ins/outs of modeling.  

When evaluating such tools there are a couple of really important features to consider:

- does the tool support multiple database vendors? (while this may not seem important b/c your website runs XYZ database today... the ability for your tool/skillset to be transferrable for your next gig is invaluable)

- does the tool do reverse-engineering of existing schemas?  (and allow foreign key inferences)

- does the tool support views, and sub-types (both complete and incomplete) in the modeling interface?

- can the tool generate ALTER statements so that existing databases can be easily updated (instead of creates)?

One feature I really liked about ER-win was that if I had an existing schema and I made changes to it, ER-Win would actually generate not just the DDL, but also the scripts that migrate the existing data to the new schema.  That was amazing!</description>
		<content:encoded><![CDATA[<p>This type of tool is also incredibly valuable for LEARNING about data modeling.  While I knew the basics from books, it was really ER-win (the grand-daddy of the data modeling space) that taught me the ins/outs of modeling.  </p>
<p>When evaluating such tools there are a couple of really important features to consider:</p>
<p>- does the tool support multiple database vendors? (while this may not seem important b/c your website runs XYZ database today&#8230; the ability for your tool/skillset to be transferrable for your next gig is invaluable)</p>
<p>- does the tool do reverse-engineering of existing schemas?  (and allow foreign key inferences)</p>
<p>- does the tool support views, and sub-types (both complete and incomplete) in the modeling interface?</p>
<p>- can the tool generate ALTER statements so that existing databases can be easily updated (instead of creates)?</p>
<p>One feature I really liked about ER-win was that if I had an existing schema and I made changes to it, ER-Win would actually generate not just the DDL, but also the scripts that migrate the existing data to the new schema.  That was amazing!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew P. Gurzynski</title>
		<link>http://blog.blakeperdue.com/2008/11/16/app-review-sqleditor/comment-page-1/#comment-883</link>
		<dc:creator>Andrew P. Gurzynski</dc:creator>
		<pubDate>Wed, 19 Nov 2008 03:25:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.blakeperdue.com/?p=443#comment-883</guid>
		<description>While I am not a Mac user this tool looks very similar to tools similar to many Entity/Relationship modeling tools that currently exist for the Wintel platform.  

ER Diagrams are useful for the simple reason that a picture is worth a thousand words.  A graphical representation is easier to look at and understand than SQL DDL statements.  

It looks like SQLEditor is a tool that allows you to create a graphical representation of your database and then create the SQL DDL (Data Definition Language) statements to create that actual tables in a target database.  

Again, I am not very familiar with the Mac environment and am not aware of any similar tools, but I would have to think they exist.  </description>
		<content:encoded><![CDATA[<p>While I am not a Mac user this tool looks very similar to tools similar to many Entity/Relationship modeling tools that currently exist for the Wintel platform.  </p>
<p>ER Diagrams are useful for the simple reason that a picture is worth a thousand words.  A graphical representation is easier to look at and understand than SQL DDL statements.  </p>
<p>It looks like SQLEditor is a tool that allows you to create a graphical representation of your database and then create the SQL DDL (Data Definition Language) statements to create that actual tables in a target database.  </p>
<p>Again, I am not very familiar with the Mac environment and am not aware of any similar tools, but I would have to think they exist.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PlexXoniC</title>
		<link>http://blog.blakeperdue.com/2008/11/16/app-review-sqleditor/comment-page-1/#comment-873</link>
		<dc:creator>PlexXoniC</dc:creator>
		<pubDate>Tue, 18 Nov 2008 16:35:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.blakeperdue.com/?p=443#comment-873</guid>
		<description>I really think this could save me a ton of time designing table structures, thanks for the link!</description>
		<content:encoded><![CDATA[<p>I really think this could save me a ton of time designing table structures, thanks for the link!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ratan</title>
		<link>http://blog.blakeperdue.com/2008/11/16/app-review-sqleditor/comment-page-1/#comment-866</link>
		<dc:creator>ratan</dc:creator>
		<pubDate>Tue, 18 Nov 2008 08:56:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.blakeperdue.com/?p=443#comment-866</guid>
		<description>A UI tool like SQL editor is always useful. For complex databases the development start from the ER diagrams and a utility which can convert the diagram to the tables is really useful. It can save lots of time, its importance can be really appreciated in time critical development. It has the potential to remove lots of typos that we inherently make.</description>
		<content:encoded><![CDATA[<p>A UI tool like SQL editor is always useful. For complex databases the development start from the ER diagrams and a utility which can convert the diagram to the tables is really useful. It can save lots of time, its importance can be really appreciated in time critical development. It has the potential to remove lots of typos that we inherently make.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chris t</title>
		<link>http://blog.blakeperdue.com/2008/11/16/app-review-sqleditor/comment-page-1/#comment-861</link>
		<dc:creator>chris t</dc:creator>
		<pubDate>Tue, 18 Nov 2008 03:55:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.blakeperdue.com/?p=443#comment-861</guid>
		<description>This is a more user friendly application, better than the tools that come from SQL Server.

Though this will likely need to be able to create sql that is specific to the different flavors of SQL: MS SQL Server, MS Access, Foxpro, Sysbase,etc.</description>
		<content:encoded><![CDATA[<p>This is a more user friendly application, better than the tools that come from SQL Server.</p>
<p>Though this will likely need to be able to create sql that is specific to the different flavors of SQL: MS SQL Server, MS Access, Foxpro, Sysbase,etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam</title>
		<link>http://blog.blakeperdue.com/2008/11/16/app-review-sqleditor/comment-page-1/#comment-854</link>
		<dc:creator>Sam</dc:creator>
		<pubDate>Mon, 17 Nov 2008 18:09:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.blakeperdue.com/?p=443#comment-854</guid>
		<description>I haven&#039;t previously used SQL Editor, but I am going to explore the idea of doing so now. Thanks!</description>
		<content:encoded><![CDATA[<p>I haven&#8217;t previously used SQL Editor, but I am going to explore the idea of doing so now. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hanawriter</title>
		<link>http://blog.blakeperdue.com/2008/11/16/app-review-sqleditor/comment-page-1/#comment-849</link>
		<dc:creator>hanawriter</dc:creator>
		<pubDate>Mon, 17 Nov 2008 15:05:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.blakeperdue.com/?p=443#comment-849</guid>
		<description>I&#039;ve used Microsoft Access before to make databases.  When the database file becomes too big the program becomes so slow.  It is quite easy to learn and use though.  SQLEditor seems to be an easy way to transition from Access to mysql.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve used Microsoft Access before to make databases.  When the database file becomes too big the program becomes so slow.  It is quite easy to learn and use though.  SQLEditor seems to be an easy way to transition from Access to mysql.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vidula ashok</title>
		<link>http://blog.blakeperdue.com/2008/11/16/app-review-sqleditor/comment-page-1/#comment-843</link>
		<dc:creator>vidula ashok</dc:creator>
		<pubDate>Mon, 17 Nov 2008 06:12:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.blakeperdue.com/?p=443#comment-843</guid>
		<description>I have studied IBM Mainframe and knows how important SQL is. It is very tedious to write the code without making mistakes. I think SQLEditor could be useful when lots of tables and data are involved. </description>
		<content:encoded><![CDATA[<p>I have studied IBM Mainframe and knows how important SQL is. It is very tedious to write the code without making mistakes. I think SQLEditor could be useful when lots of tables and data are involved.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
