project_sqldevtools/index.html - gerrit/www.eclipse.org/datatools - Git at Google

 <!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
 <html><head>
 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

 <title>DTP SQL Development Tools Project</title><link rel="stylesheet" href="../../default_style.css"><link></head>

 <body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">
 &nbsp;
 <table border="0" cellpadding="2" cellspacing="5" width="100%">
   <tbody><tr>
     <td align="left" width="60%"><font class="indextop">sql development tools project</font><br>
       <font class="indexsub">Project Home Page </font></td>
     <td width="40%"><img src="../../images/Idea.jpg" align="middle" height="86" hspace="50" width="120"></td>
   </tr>
 </tbody></table>

 <table border="0" cellpadding="2" cellspacing="5" width="100%">
   <tbody><tr>
     <td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font color="#ffffff" face="Arial,Helvetica">Project Overview</font></b></td>
   </tr>

   <tr>
     <td>
       <p>The SQL Development Tools project provides frameworks and tools for deep and broad SQL support.</p>
     </td>
   </tr>
 </tbody></table>
 <!--
 <table border="0" cellpadding="2" cellspacing="5" width="100%">
   <tbody>
     <tr>
       <td align="left" bgcolor="#0080c0" valign="top"><b><font face="Arial,Helvetica"><font color="#ffffff">What's New</font></font></b></td>
     </tr>
      <tr><td>
       <p><img src="../../images/Adarrow.gif" width="16" height="16" border="0">
     	  <a href="plans/SQL Dev Tools Plan.html" target="main"><b>November 28: </b>Development schedule posted</a>
       </p>
     </td></tr>
 </tbody></table>
 -->
 <table border="0" cellpadding="2" cellspacing="5" width="100%">
   <tbody><tr>
     <td align="left" bgcolor="#0080c0" valign="top"><b><font face="Arial,Helvetica"><font color="#ffffff">Project Components</font></font></b></td>
   </tr>
   <tr>
     <td>
       <ul><li><p><b>Routines Editor Framework</b><br/><br/>An extensible framework for editing database routines and SQL statements.
       Vender-specific extensions enable specialized support for particular databases.</p></ul>
 <!--
 	  <ul><LI><P><b>Routines Debugger Framework</b><br/><br/>While routine debug support varies widely in existing database offerings,
 	  the Routines Debugger Framework will provide an extensible base enabling debug support for specific cases in a manner consistent
 	  with existing Eclipse debug infrastructure.</p></ul>
 -->
 	  <ul><li><p><b>SQL Query Parser</b><br/><br/>Although SQL is defined by a standard, several major dialects exist. Thus,
 	  while the standard must be supported, practicality also demands flexibility in adjustment to dialects. The SQL Query
 	  Parser meets these needs by providing an extensible framework, enabling dialect-aware SQL components and tools.</p>
 	  <p><b>IMPORTANT: </b><a href="sqltools_doc/sqlqueryparser_lpg_readme.html">Obtaining lpg.jar required by the SQL Query Parser</a></b></p>
 	  <p><i>Using the SQL Query Parser</i> (<a href="sqltools_doc/SQL Query Parser User documentation.htm">HTML</a>)</p>
 	  </ul>
 <!--
 	  <ul><li><p><b>SQL Execution Plan Framework</b><br/><br/>The ability to understand how a SQL evaluation engine will
 	  execute a given query is vital in tuning queries to optimize performance. The SQL Execution Plan Framework will provide
 	  a means for capturing and presenting execution plans in a generic fashion, enabling extends to customize support for specific
 	  SQL execution engines.</p></ul>
 -->
 	  <p>The tools include:</p>
 	  <ul><li><p><b>SQL Editor</b><br/><br/>The SQL Editor will provide an exemplary tool for standard text-based editing
 	  of SQL statements. Providing content assist tied to the SQL Model, syntax colorization, and multiple statement support,
 	  this editor will provide an essential tool for data-centric development.</p></ul>
 	  <ul><li><p><b>Visual SQL Builder</b><br/><br/>The Visual SQL Builder allows for graphical editing of SQL, raising the
 	  level of abstraction, increasing developer productivity, and making query construction possible for a wider user base.</p></ul>
 	  <ul><li><p><b>Results View</b><br/><br/>The Results View displays the output of routine or SQL statement execution in a tabular
 	  form typical of SQL result sets. These results can be exported to persistent storage in a variety of formats and reloaded at a
 	  later time into the results view.</p></ul>
 	  <ul><li><p><b>Script History</b><br/><br/>Typically a number of scripts will be executed repeatedly during the course
 	  data-centric development. The ability to retain a history of these queries and thereby quickly repeat execution of
 	  them and view results increases productivity. The Script History is a view meeting these needs, based on a development session.</p></ul>
     </td>
   </tr>
 </tbody></table>
 </body></html>
	<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
	<html><head>
	<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

	<title>DTP SQL Development Tools Project</title><link rel="stylesheet" href="../../default_style.css"><link></head>

	<body alink="#ff0000" bgcolor="#ffffff" link="#0000ee" text="#000000" vlink="#551a8b">

	<table border="0" cellpadding="2" cellspacing="5" width="100%">
	<tbody><tr>
	<td align="left" width="60%"><font class="indextop">sql development tools project</font><br>
	<font class="indexsub">Project Home Page </font></td>
	<td width="40%"><img src="../../images/Idea.jpg" align="middle" height="86" hspace="50" width="120"></td>
	</tr>
	</tbody></table>

	<table border="0" cellpadding="2" cellspacing="5" width="100%">
	<tbody><tr>
	<td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font color="#ffffff" face="Arial,Helvetica">Project Overview</font></b></td>
	</tr>

	<tr>
	<td>
	<p>The SQL Development Tools project provides frameworks and tools for deep and broad SQL support.</p>
	</td>
	</tr>
	</tbody></table>
	<!--
	<table border="0" cellpadding="2" cellspacing="5" width="100%">
	<tbody>
	<tr>
	<td align="left" bgcolor="#0080c0" valign="top"><b><font face="Arial,Helvetica"><font color="#ffffff">What's New</font></font></b></td>
	</tr>
	<tr><td>
	<p><img src="../../images/Adarrow.gif" width="16" height="16" border="0">
	<a href="plans/SQL Dev Tools Plan.html" target="main"><b>November 28: </b>Development schedule posted</a>
	</p>
	</td></tr>
	</tbody></table>
	-->
	<table border="0" cellpadding="2" cellspacing="5" width="100%">
	<tbody><tr>
	<td align="left" bgcolor="#0080c0" valign="top"><b><font face="Arial,Helvetica"><font color="#ffffff">Project Components</font></font></b></td>
	</tr>
	<tr>
	<td>
	<ul><li><p><b>Routines Editor Framework</b><br/><br/>An extensible framework for editing database routines and SQL statements.
	Vender-specific extensions enable specialized support for particular databases.</p></ul>
	<!--
	<ul><LI><P><b>Routines Debugger Framework</b><br/><br/>While routine debug support varies widely in existing database offerings,
	the Routines Debugger Framework will provide an extensible base enabling debug support for specific cases in a manner consistent
	with existing Eclipse debug infrastructure.</p></ul>
	-->
	<ul><li><p><b>SQL Query Parser</b><br/><br/>Although SQL is defined by a standard, several major dialects exist. Thus,
	while the standard must be supported, practicality also demands flexibility in adjustment to dialects. The SQL Query
	Parser meets these needs by providing an extensible framework, enabling dialect-aware SQL components and tools.</p>
	<p><b>IMPORTANT: </b><a href="sqltools_doc/sqlqueryparser_lpg_readme.html">Obtaining lpg.jar required by the SQL Query Parser</a></b></p>
	<p><i>Using the SQL Query Parser</i> (<a href="sqltools_doc/SQL Query Parser User documentation.htm">HTML</a>)</p>
	</ul>
	<!--
	<ul><li><p><b>SQL Execution Plan Framework</b><br/><br/>The ability to understand how a SQL evaluation engine will
	execute a given query is vital in tuning queries to optimize performance. The SQL Execution Plan Framework will provide
	a means for capturing and presenting execution plans in a generic fashion, enabling extends to customize support for specific
	SQL execution engines.</p></ul>
	-->
	<p>The tools include:</p>
	<ul><li><p><b>SQL Editor</b><br/><br/>The SQL Editor will provide an exemplary tool for standard text-based editing
	of SQL statements. Providing content assist tied to the SQL Model, syntax colorization, and multiple statement support,
	this editor will provide an essential tool for data-centric development.</p></ul>
	<ul><li><p><b>Visual SQL Builder</b><br/><br/>The Visual SQL Builder allows for graphical editing of SQL, raising the
	level of abstraction, increasing developer productivity, and making query construction possible for a wider user base.</p></ul>
	<ul><li><p><b>Results View</b><br/><br/>The Results View displays the output of routine or SQL statement execution in a tabular
	form typical of SQL result sets. These results can be exported to persistent storage in a variety of formats and reloaded at a
	later time into the results view.</p></ul>
	<ul><li><p><b>Script History</b><br/><br/>Typically a number of scripts will be executed repeatedly during the course
	data-centric development. The ability to retain a history of these queries and thereby quickly repeat execution of
	them and view results increases productivity. The Script History is a view meeting these needs, based on a development session.</p></ul>
	</td>
	</tr>
	</tbody></table>
	</body></html>