On 9/12/07, Law, Bill <blaw@...> wrote:
> > Greetings,
> We are considering using SQuirreL as the base platform for developing a
> plugin which provides creating, deleting, editing, and browsing of SQL
> metadata objects for one of our own database products. Much like is
> provided by the pgAdmin tool. Of special interest is updating metadata
> for foreign databases, foreign tables, regular tables, native files,
> views, and users. We would prefer to do things the SQuirreL way, and
> better yet to take advantage of existing, or soon to exist, SQuirreL
> features. But SQuirreL 2.5 seems to currently be a little weak in the
> areas of editing metadata.
> In general, what are the SQuirreL team's plans or roadmap for providing
> metadata updatability?
> In particular, does the SQuirreL team recommend and plan to enhance the
> Refactoring plugin?
I wrote the refactoring plugin and it meets my needs at present. As
far as enhancements go, the features I would probably work on next
would be the ability to add/modify/drop indexes and FKs.
To support a new database, there is a bit of work to be done
developing a dialect for it. I would need an SQL reference guide for
the database that explains the grammar for adding/dropping/modifying
columns and primary keys as well as a description of supported data
types and their precision or maximum length. Ideally, I would be able
to connect to a running instance of the database for testing. This
isn't strictly necessary, but it helps to speedup iterations. You
contrasted "foreign tables" with "regular tables". Can you explain
the difference between the two? What is your database implementation
I'm currently developing a difference plugin that will allow you to
compare all columns in two tables for differences. I'm wrapping that
up at the moment, and I don't know at the moment when I'll get back to