On Sat, Sep 13, 2008 at 11:52 AM, M@rton Akos <makos999@gmail.com> wrote:
> Hi Developers,
>
> I'm on a half work to write a searchbar into pgadmin3.
> I think the search engine would be locate a self-sufficing float
> panel, like the object browser.
It should probably be part of the object browser, as that is what you
are search. Perhaps an expandable panel at the top or bottom.
> I've been writing a method to find object(s) in the tree and then
> collect them into another tree in the searchbar to show the result.
> The user could chose the object and via the searchbar select the item
> in the object browser.
> It's necessary when the tree in the object browser is too long and i
> forgot the name of tables.
> Please take me your opinions and tips about the code!
The first thing that springs to mind is that you cannot just search
the object browser, because a large percentage of it won't necessarily
be populated when the search is done (and the user does not
necessarily know what is and isn't populated at any given time). That
actually makes this quite difficult to do - searching every database
on every server for an object (of potentially unknown type) would be
extremely expensive once you get past just a couple of databases in
total. That cost could be reduced by requiring that a type is
specified, and further by restricting searches to a specific database.
I think we'd need to see a mockup screenshot of the UI to see how that
might pan out, as well as a rough outline of how the code will
actually work.
Sounds like an interesting project though.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers
No comments:
Post a Comment