table editing application

From: Eric Lenio (dbi-users_at_lenio.net)
Date: 01/23/04 

Date: Fri, 23 Jan 2004 15:11:12 -0500
To: dbi-users@perl.org

I have written a perl application using the DBI and Curses modules that allows
you to pick a table from a given schema, and then opens it up either in a
"tabular" MS Excel-like way, or in a "form" based mode. From this point you
can browse, update, insert, or delete data, with the option to simple "where"
clauses. For those of you not familiar with Curses, it is a library of screen
functions that lets you write simple GUI's for terminals. I wrote the app
because:

1. I work mostly inside xterm windows, with a need to frequently browse/edit
data in many different schemas, and I have no patience using tools like
Oracle's DBA Studio because it just slows me down.
2. I use multiple relational databases so DBI makes it possible (well, in
theory) to use the app with any DBD::* module that also supports a row ID
pseudocolumn. So far I've successfully used Oracle, Ingres, and Postgres.
3. I can do Perl-like things with my data much easier, vs. struggling to learn
the rdbms-specific syntax that accompanies each rdbms.
4. My client uses it.
5. It is cross-platform. I currently use it with Solaris and Linux, but I
would also like to add Windows support too.
6. DBI has helped me immeasurably in my work and I'd like to contribute back to
the community.

I'm attempting to see if there is any interest out there for me to formalize
things and distribute this code as a module on CPAN. If you do have interest
drop me an email and let me know if you have feature requests or suggestions,
or maybe you'd like to help test, or maybe you just want to stay apprised of
the progress of things. If enough are interested, I can set up a listserv to
handle things.

Currently I am re-writing the app from the ground up as I have learned quite a
bit more about DBI and Curses in the past 8 months or so, and I want to
leverage that knowledge to build a better app... there are actually many new
effiencies I want to add back in.

Thanks,
Eric.

Relevant Pages

  • Re: DBI primary_key tests fail: oracle 8
    ... The DBI doesn't define a portable way to determine the 'current schema'. ... Of course there are ways to do it for Oracle but I can't remember it off-hand. ... $dbh->isn't part of the DBI spec and shouldn't be relied upon. ... > If I manually set the 2nd arg to the true oracle user then the tests pass. ...
    (perl.dbi.users)
  • RE: Oracle and dbh -> last_insert_id
    ... to use the dbi last_insert_id. ... I've tried various values for catalog and schema, ... I would doubt that dbd Oracle supports this. ... RETURNING empno ...
    (perl.dbi.users)
  • Re: DBI primary_key tests fail: oracle 8
    ... Hi Tim, I believe you could use this snippet to determine the current schema if ... > The DBI doesn't define a portable way to determine the 'current schema'. ... > Of course there are ways to do it for Oracle but I can't remember it off-hand. ...
    (perl.dbi.users)
  • Re: table editing application
    ... creating a plug-in to work with DBI::Shell. ... > bit more about DBI and Curses in the past 8 months or so, ... > effiencies I want to add back in. ...
    (perl.dbi.users)
  • Oracle and dbh -> last_insert_id
    ... OS: GNU/Linux ... DBI: V 1.48 ... I've tried various values for catalog and schema, ...
    (perl.dbi.users)