Frequently Asked Questions

Q: What is HTSQL?

A: Hyper Text Structured Query Language is a straightforward and robust way to retrieve data from databases using URLs (HTTP requests). HTSQL allows complete database access through a web browser or other networked application without additional programming.  By getting to data faster, at lower cost, and more easily both technical and non-technical users can make decisions with more confidence.

Q: What has Prometheus Research achieved with HTSQL?

A: HTSQL unlocks sources of valuable data that are inaccessible due to technical, resource and budget constraints. With the explosion of interest in Web 2.0 and mobile application development, there are thousands of potential new users for these data sources. HTSQL aims to do for data what HTTP has done for documents.

Q: What do I need to do to use HTSQL?

A: You need the HTSQL server software and a SQL-compliant database. Currently, HTSQL supports Oracle, MS SQL Server and the open source PostgreSQL database, with Microsoft SQL and MySQL support to follow shortly.

Q: Is HTSQL open source?

A: HTSQL is based on open source technology. Prometheus makes HTSQL available to users of non-commercial databases (like PostgreSQL) royalty-free, meaning there is no license fee for its use.

Q: Is HTSQL standards based?

A: Yes. HTSQL is based on standards including SQL (ISO9075-1993), HTTP (RFC2616), and URI (RFC3986).

Q: What browsers does HTSQL work with?

A: Any software that can send an HTTP (web) request and receive HTML, XML or plain text can use HTSQL. This includes browsers on all platforms and mobile devices.

Q: How is HTSQL different from other approaches to accessing data on the Internet?
 
A:  HTSQL is different because it does not require use of a specific architecture or programming language. HTSQL uses HTTP queries—the universal language of the web—to pass queries to the database. Advantages of this approach include:

•    Reducing time spent on development and maintenance
•    Creating faster, more reliable data, more easily
•    Making decision making easier, faster, and with more confidence that data is reliable
•    Supporting an unlimited number of front-end applications (web, mobile, etc.) with a single database access approach
•    Lowering the barrier of entry for database users and developers
•    Simplifying security and other administrative tasks through use of a universally accepted standard protocol (HTTP)

Q: How does HTSQL compare to web services?

A: Web services provide a programmatic interface to applications that can be accessed by other applications. HTSQL is a simple, URL-based method for retrieving data that can be used by either people or applications. HTSQL can be easier to use than web services, particularly for novice developers.

Q: Who is a typical user of HTSQL?

A: HTSQL is for both technical and non-technical data “power users” and multi-taskers who straddle business and technical roles in their organizations. They understand the data and have great ideas for how to use it, but may not have the time or resources to devote to create and maintain complex applications. They include department and project leads, researchers, webmasters, database administrators, and interface developers.

Q: How does HTSQL help organizations?

A: HTSQL helps organizations be more productive by reducing bottlenecks created by limited technical resources. It lets organizations leverage investments made in collecting and maintaining data by allowing end users to discover and promote new uses for it. HTSQL also reduces costs for both creating and maintaining applications by simplifying their development and requiring fewer technical skills.

Q: How does HTSQL help database administrators?

A:  Especially when maintaining large, complex databases, DBAs have their hands full with administrative, maintenance and security tasks. HTSQL removes the burden of responding to end user requests for reports while allowing DBAs to retain control of database access. In addition, it allows DBAs and busy IT departments to focus on truly complex requests while leaving general requests to non-technical users.

Q: How does HTSQL help developers?

A: HTSQL allows developers to create simple, flexible architectures for accessing data in a variety of ways without rewriting and retesting code. Because HTSQL queries are simple HTTP requests, they are compatible with virtually any web programming language, application server, or UI tool. By replacing complex “middleware” for database access, HTSQL reduces the cost of maintaining and enhancing applications and allows for more flexibility in IT hiring. 

Q: What skills are required to use HTSQL?

A: Users should be familiar with the contents of the database. Experience with spreadsheet and search concepts (pattern matching, pivot tables, etc.) is a plus but not necessary. Most users pick up the basics of HTSQL within minutes.

Q: What is the output of an HTSQL query?

A: HTSQL will automatically generate XML, HTML, TXT, or CSV files. Other text-based file formats may be available on request.

Q: Does HTSQL only handle simple SQL queries?

A: HTSQL can perform complex queries, including multiple joins and filter conditions, numerical operations, and string operations in a single query. HTSQL supports SQL.

Q: Is HTSQL only for reading data from databases?

A: HTSQL supports insert, update, delete, and merge operations (providing the user trying to perform these operations has database permission to do so).

Q: Will HTSQL compromise the security of my database?

A: HTSQL does not bypass or override security measures already in place on your database. Authentication and authorization continue to be handled by the database, along with any additional security measures you wish to implement through our server- or client-based application. Because it filters queries before sending them to the database, HTSQL may help protect your database against SQL injection attacks and other stresses caused by badly formed queries.

Q: Will HTSQL overload my database?

A: HTSQL queries are no different from other web queries. However, since HTSQL makes it easier to query your database, you should carefully consider who and how the database will be accessed through HTSQL and related applications so you can prepare, if necessary, for additional load.

Q: How is HTSQL different from interactive web interface?

HTSQL is the perfect complement to interactive Web 2.0-type applications. HTSQL allows web designers and developers to perform sophisticated database queries with a simple URL. HTSQL returns data in easy-to-use XML form, perfect for “grid widgets” and a variety of other client-side applications. For companies that don’t have or don’t need interactive development, HTSQL can stand alone, working in the browser without an interface, or with its own built-in interactive query tool.

Q: How long does it take to set up?

A: HTSQL takes about an hour to install and configure. Planning can take a bit longer, depending on the application.

Q: What are the benefits of HTSQL over a remote access query or reporting tool?

A: HTSQL does not require installing and maintaining client software. All queries, updates, and deletes can be done through a web browser. Since it runs over HTTP, HTSQL doesn’t require that special ports or protocols be used.
 
Q: Is training needed? What type of training is available for end-users?

A: Prometheus provides full documentation, including an online tutorial, and can develop custom training programs. However, most users are able to master the basics of HTSQL with little to no training.

Q: How do you handle support requests from end-users who have problems with their queries?

A: Prometheus offers first- and second-tier support plans for customers who require help desk support.

Q: What security features are available to restrict access? Can certain authorized users be restricted to only certain database tables, while other users can access all database tables?

A: Yes. In addition to supporting user roles as defined in the database, HTSQL allows specific tables to be excluded from all queries. HTSQL also implements role-based security at the row level rather than just at the table level.

Q: How does a user control the look of the table of query results that's displayed? Are other formatting options for the output table available (shading, colors, etc.)?

A: CSS style sheets control HTML output. Customers can develop their own or request custom development of style sheets for specific applications (to match website look and feel, for mobile devices, etc.).

Q: Can the user choose from a library of reports that database developers previously created?

A: HTSQL requests are just URLs. As such, “saving” a report is as easy as bookmarking it in a browser or linking to it from an email or web page. This is a much simpler and more intuitive way to share reports than saving queries.

Q: Does the system support "stored procedures,” "views,” and other pre-coded items that could be created by database developers for end-users?

A: Stored procedures are on the current roadmap for HTSQL.

Q: How does a user access the string functions, such as CONCAT?

A: HTSQL supports a full range of string functions including concatenation. For more, please see the HTSQL reference.

Q: Can a user create temporary variables (e.g., @starting_id) for use in later queries?

A: Variables can be set queries. However, since HTTP is a stateless protocol, state must be maintained somewhere else (such as in an application).

Q: How does a user access the date and time functions such as DATE_FORMAT, TO_DAYS, and ADDTIME?

A: HTSQL supports a full rate of date and time functions. For more, please see the HTSQL reference.