Preview jTalk

black

Database Queries and Results Parsing

Making the business case for jTalk.
The following preview outlines the key features and benefit analysis of jTalk, incorporating screenshots and example code snippets.

jTalk solves the following critical business problems experienced by all web application developers:


shim

Advanced developers are well aware that most web applications need to incorporate dynamic data into database queries. Using traditional JSP and/or standard Java syntax often means creating cumbersome variables to store and retrieve the dynamic query as well as having to handle the parsing and encoding of SQL elements.

When things go wrong, tracking bugs becomes near impossible. Here's our solution:

Built from the Ground Up for SQL

At the center of any web application is the database. At the heart of the database is SQL, the uniform standard for talking to databases. In building jTalk's architecture, we knew we needed to fully embrace both in order to make jTalk the natural choice.


  <jtalk:sql config="website">
    SELECT * FROM News WHERE Year = '2002' ORDER BY OrderDate DESC 
  </jtalk:sql>

As a result, every effort has been made to allow you to talk to your database using the language you already know, SQL, without involving yourself in the ancillaries and mechanics. Simply write your SQL query within the jTalk SQL tags in your JSP pages. You will never see a proprietary approach to data retrieval in jTalk.

Dynamic Queries

As we mentioned earlier, jTalk was designed around the database- the heart of your web application. As such, every jTalk tag that outputs a result, can be used in a database query. Tags can also perform SQL encoding, automatically converting the results to SQL encoded values! Queries can contain logic functions, that will be pre-processed before execution, giving you the kind of control over information everyone is looking for. Nothing less. Nothing less than astonishing.


  <jtalk:sql config="website" maxRows="all">
    SELECT * FROM News
    <jtalk:if>
      <jtalk:condition>
        <jtalk:requestParameter name="year"/> .eq. 2002
      </jtalk:condition>
      <jtalk:then>
        WHERE Year = '<jtalk:requestParameter name="year"/>'
      </jtalk:then>
    </jtalk:if>
    ORDER BY OrderDate DESC 
  </jtalk:sql>

Reuse Query Results within Queries

Going further, you can use the results of one query within the statement of the next query! Even giving you the ability to perform joins on completely separate databases. Resulting in content that is as alive as your databases themselves. SQL programmers will know this solves the business problem of returning data where joins may not.

Store Query Results in Scopes

Query once, use your results anywhere. jTalk query results can be stored in your application page, request or session scopes. Meaning that you can use query results anywhere your site visitors go without having to perform additional queries, if you so choose. This powerful feature can drastically improve performance as data is accessed directly from memory.

Parse Through Results

Displaying the results of a database query can be tricky. Typical JSP/Java syntax requires an extensive knowledge of all database structure. Column results must be fetched using a unique method for each column type. jTalk makes you more productive by alleviating this step and allowing you to retrieve column results without any database structure knowledge whatsoever. Additionally, the jTalk database tags can easily localize data for any given country.

Result Set Parsing

jTalk includes simple tags used to access query results meta-data. From finding out how many results were found, determining whether there are more results not displayed, even building links to the next set of results. jTalk can be used to display a limited number of results at a time and automatically build links to easily navigate through the entire result set.

Next »


shim