3 ms·

Thanks for the comments, I do appreciate the input. A couple of advantages over pgAdmin for an offsite database is that it will not drop connections, and it can

Thanks for the comments, I do appreciate the input. A couple of advantages over pgAdmin for an offsite database is that it will not drop connections, and it can easily be configured for SSL using https. Also, clients don't have to install anything. Feature-wise the focus at this point has mostly been on powerful data navigation, i.e. you can do a quick search for a customer id, click the reference to the purchase order table, click to download a pdf contract directly from a binary field (just an example). The tool provides significant time-savings for these tasks, though you may not discover this unless you delve into the product a little. More generally there are many little productivity improvements and details that support the user that all add up to provide value, which may not be noticed at a quick glance. I hope to be able to communicate these as efficiently as possible. Going forward there is a lot of room for the kind of analytical features you mentioned. This is still an early version of the product with focus on core administration tasks. In fact management of running processes is due in the next release.

kls 17y ago
A couple of things, powerful data navigation and export to pdf from the UI are rely nice features and they will make life easier for the end user, but in my experience the main user of a DB admin application are developers, DBA's and admins. Most of which are not as concerned with the actual contents of the data, as they are with the structures of the data as well as the performance of the data. Developers general concern themselves with the data when they are setting up test, or diagnosing a data related problem but in the coarse of a day most of their focus is on the structure and performance of the data and database. The point being, generally your call center rep or your accountant (the end user) uses a custom interface dedicated to data navigation and data viewing (coupled with workflow) these features will most likely not be exposed to them and they are the users most advantaged by them, particularly the export to PDF feature. Again, please don't take this as knocking your hard work, I think that powerful data navigation is important for those times that you do have to directly manage the data and think other DB admin front ends are severely lacking in that departments, but I urge you to keep in mind that in most organizations almost all the end users that are interested in the actual data are buffered away from a raw DB interface, even report writers who know SQL fairly well are buffered with tools such as Cognos and Crystal Reports. But I think you have the basis to cure a pain point that plagues a lot of organizations given that you now have a good base product to build a robust development tool on. A portion of (software) developers do not like and look at relational databases as second class to actually writing software. If you can mold your tool in to providing deep analysis and diagnostics and marry that with solution engine that provides recommendations on how to optimize and refine the data structure and query structures so that they are more performant, more secure, less resource intensive and you can do this in a seamless way you are scratching an itch that a good portion of developers cant reach.
- johnyzee 17y ago
  Again, thanks for your comments, I believe you are right. Particularly administrators are less concerned with what is in the database than how the database is organized and performs - for them the product does not currently offer any particular advantages at this stage. I will seriously consider how to better address this, given that administrators are arguably the most obvious consumers of this kind of product. At this point the product addresses many of my own pain points of modelling and troubleshooting databases and data related issues from the point of view of a developer. Test departments too will benefit a lot from these features. As for the other groups it is true that they will mostly use a dedicated interface, yet for the time when the occasional manager or supporter does need/want to check out something he can. That is mostly an added benefit from the product being (hopefully) so easy to use. Thanks for giving me something to consider for the future direction of the product. By the way, the PDF example just demonstrates how the tool lets you download a file directly from a binary field in a table row (f.ex. bytea type column). It can be any file type, some use the database to store images, for example. Similarly, you can upload a file from your PC directly into a binary field in your table. It is a good example of how the tools makes an otherwise involved task very simple.
- deleted 17y ago
  [deleted]

kls 17y ago

A couple of things, powerful data navigation and export to pdf from the UI are rely nice features and they will make life easier for the end user, but in my experience the main user of a DB admin application are developers, DBA's and admins. Most of which are not as concerned with the actual contents of the data, as they are with the structures of the data as well as the performance of the data. Developers general concern themselves with the data when they are setting up test, or diagnosing a data related problem but in the coarse of a day most of their focus is on the structure and performance of the data and database. The point being, generally your call center rep or your accountant (the end user) uses a custom interface dedicated to data navigation and data viewing (coupled with workflow) these features will most likely not be exposed to them and they are the users most advantaged by them, particularly the export to PDF feature. Again, please don't take this as knocking your hard work, I think that powerful data navigation is important for those times that you do have to directly manage the data and think other DB admin front ends are severely lacking in that departments, but I urge you to keep in mind that in most organizations almost all the end users that are interested in the actual data are buffered away from a raw DB interface, even report writers who know SQL fairly well are buffered with tools such as Cognos and Crystal Reports. But I think you have the basis to cure a pain point that plagues a lot of organizations given that you now have a good base product to build a robust development tool on. A portion of (software) developers do not like and look at relational databases as second class to actually writing software. If you can mold your tool in to providing deep analysis and diagnostics and marry that with solution engine that provides recommendations on how to optimize and refine the data structure and query structures so that they are more performant, more secure, less resource intensive and you can do this in a seamless way you are scratching an itch that a good portion of developers cant reach.

johnyzee 17y ago
Again, thanks for your comments, I believe you are right. Particularly administrators are less concerned with what is in the database than how the database is organized and performs - for them the product does not currently offer any particular advantages at this stage. I will seriously consider how to better address this, given that administrators are arguably the most obvious consumers of this kind of product. At this point the product addresses many of my own pain points of modelling and troubleshooting databases and data related issues from the point of view of a developer. Test departments too will benefit a lot from these features. As for the other groups it is true that they will mostly use a dedicated interface, yet for the time when the occasional manager or supporter does need/want to check out something he can. That is mostly an added benefit from the product being (hopefully) so easy to use. Thanks for giving me something to consider for the future direction of the product. By the way, the PDF example just demonstrates how the tool lets you download a file directly from a binary field in a table row (f.ex. bytea type column). It can be any file type, some use the database to store images, for example. Similarly, you can upload a file from your PC directly into a binary field in your table. It is a good example of how the tools makes an otherwise involved task very simple.
deleted 17y ago
[deleted]