[Geany-Devel] Looking for features for a SQL plugin

[Frank Lanitz]

On Tue, 25 Mar 2014 08:45:21 +1100
Lex Trotman <elextr at gmail.com> wrote:

> [...]
> 
> I guess for my vision of this sort of database development UI tool I
> am channelling my secret shameful past use of Microsoft Access, whilst
> lots of it was bad, some of its interactive stuff was kind of useful
> :)

Well, this is something at least /me will not build ;)

> >> > That would be a reasonable minimum.  We could extend it from
> >> > there to:
> >> >
> >> > Show tables in the current database on the side panel, expandable
> >> > to show the columns
> >>
> >> Editable if supported by the underlying database, what about
> >> creating tables as well?
> >
> > CREATE TABLE "foo";
> > should be not too complicated for everyone in first step IMHO.
> 
> Ummm, I was thinking of defining the columns too :)  and for use
> during development it would be nice if it did the drop and re-create
> if the table already existed, or modified the columns if supported by
> the particular database.  And maybe transferred the existing contents
> too :)

Puh. This sounds like a huge thing to be done. But well... should be
possible some time.

> >> > Allow editing of the cells in the table output
> >> >
> >>
> >> Which is where outputting to the edit buffer helps, save means
> >> commit changes?
> >
> > Well... This is something, I was thinking of not having -- at least
> > on versions. I just don't think it's needed to often by a
> > developer. And everyone else could use pgadmin/phpmyadmin/*
> 
> Well, you did ask for suggestions :)
> 
> Anyway XXXadmin are specific tools, following on from Stevens comment,
> the Geany tools should be database independent.  And editing data to
> correct the update you just tried would be useful.

Yes.

> >> > Some further thoughts:
> >> >
> >> > I used SQLAlchemy for my gedit plugin (it was in python) because
> >> > it allowed connecting to various SQL databases such as MySQL,
> >> > PostgreSQL, etc If there is a way to make the output in a table
> >> > on a separate thread to not lock the UI, that would be good for
> >> > larger result sets.  We could at least create some optional
> >> > built in limit of how many results. A way to kill the query in
> >> > progress would be good
> >>
> >> In current Geany thats best handled as a subprocess, which is also
> >> a good way of handling multi-database configurability, just run the
> >> command for the particular database.
> >
> > I second that there should be a blocking UI when running a query --
> > by using the geany api it should be not often the issue anymore.
> 
> Well, good luck Frank, IIUC we can't even make modal dialogs block (at
> least on Unity and KDE :)

It depends where you are doing what ;) 
But yepp, ongoing topic.
 
> PS what about no-SQL databases, yeah I want everything ;-)

Well.... even this mail is noSQL-database, right? ....
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.geany.org/pipermail/devel/attachments/20140325/9808f09b/attachment.sig>