Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

ThinkUI SQL Client 1.0.9 (Default branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News ThinkUI SQL Client 1.0.9 (Default branch)
# 1  
Old 01-07-2009
ThinkUI SQL Client 1.0.9 (Default branch)
Image The ThinkUI SQL Client is a graphical program that allows Java developers to browse a database structure, edit data in the tables, issue SQL queries, and generate code (e.g. Java Bean, DAO, SQL queries, JSP files, etc.) based on customizable Velocity templates. License: Free To Use But Restricted Changes:
This release adds support for generating Ant scripts for executing SQL CREATE TABLE and SQL INSERT statements. Improved keyboard shortcuts have been added, as well as UNDO/REDO support in all text editors. A custom test data generation feature has been added by integrating with the ThinkUI Data Generator. In addition, this release also includes various GUI related enhancements and several bugfixes. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. SCO

SCO 6 and SQL client

Is there a open source SQL client or iSQL or any sql client that works with SCO6 openserver? And if there is where can I download it from? (1 Reply)
Discussion started by: rdhavale
1 Replies

2. Shell Programming and Scripting

(perl) Microsoft SQL Server client for solaris. cant find it...

let me save everyone the pain that it caused me. This is all free. And make sure it is in this order 1) make sure you have the latest version of perl installed 2) make sure you have NET:aemon installed 3) make sure you have RPC::PlServer & PlClient (the bundle has both) 4) make sure... (3 Replies)
Discussion started by: Optimus_P
3 Replies
Login or Register to Ask a Question

LEARN ABOUT DEBIAN

sql::translator::parser::dbi

SQL::Translator::Parser::DBI(3pm)			User Contributed Perl Documentation			 SQL::Translator::Parser::DBI(3pm)

NAME

       SQL::Translator::Parser::DBI - "parser" for DBI handles

SYNOPSIS

	 use DBI;
	 use SQL::Translator;

	 my $dbh = DBI->connect('dsn', 'user', 'pass',
	     {
		 RaiseError	  => 1,
		 FetchHashKeyName => 'NAME_lc',
	     }
	 );

	 my $translator  =  SQL::Translator->new(
	     parser	 => 'DBI',
	     dbh	 => $dbh,
	 );

       Or:

	 use SQL::Translator;

	 my $translator      =	SQL::Translator->new(
	     parser	     => 'DBI',
	     parser_args     => {
		 dsn	     => 'dbi:mysql:FOO',
		 db_user     => 'guest',
		 db_password => 'password',
	   }
	 );

DESCRIPTION

       This parser accepts an open database handle (or the arguments to create one) and queries the database directly for the information.

       The following are acceptable arguments:

       o   dbh

	   An open DBI database handle.  NB:  Be sure to create the database with the "FetchHashKeyName => 'NAME_lc'" option as all the DBI
	   parsers expect lowercased column names.

       o   dsn

	   The DSN to use for connecting to a database.

       o   db_user

	   The user name to use for connecting to a database.

       o   db_password

	   The password to use for connecting to a database.

       There is no need to specify which type of database you are querying as this is determined automatically by inspecting
       $dbh->{'Driver'}{'Name'}.  If a parser exists for your database, it will be used automatically; if not, the code will fail automatically
       (and you can write the parser and contribute it to the project!).

       Currently parsers exist for the following databases:

       o   MySQL

       o   SQLite

       o   Sybase

       o   PostgreSQL (still experimental)

       Most of these parsers are able to query the database directly for the structure rather than parsing a text file.  For large schemas, this
       is probably orders of magnitude faster than traditional parsing (which uses Parse::RecDescent, an amazing module but really quite slow).

       Though no Oracle parser currently exists, it would be fairly easy to query an Oracle database directly by using DDL::Oracle to generate a
       DDL for the schema and then using the normal Oracle parser on this.  Perhaps future versions of SQL::Translator will include the ability to
       query Oracle directly and skip the parsing of a text file, too.

AUTHOR

       Ken Y. Clark <kclark@cpan.org>.

SEE ALSO

       DBI, SQL::Translator.

perl v5.14.2							    2012-05-01					 SQL::Translator::Parser::DBI(3pm)