1 403 355 8901 info@guild1.com

Query Database

Want create site? Find Free WordPress Themes and plugins.

This action executes an ad hoc query against a database to create a table containing the results of the query. If the optional key list is input, you can use the ${key.name} syntax to substitute key values in your query. If no key list is input, the query is run once as entered. You can get keys from other databases.

  • Field

  • Label

    A label to identify the action. This label appears under the Action name inside the Action box. If this field is left blank, the default value is “Untitled.”
  • Description

    A brief explanation of what this action does inside the sequence. This description appears as a tooltip when your cursor hovers over the Action box.
  • Fail Message

    A message that identifies potential issues that could happen with this action. This fail message will appear if the action fails when you try generating the sequence. If this field is left blank, the default error message built into the action appears.
  • User

    An optional user ID to use when running the SQL query.
  • Password

    An optional password is used when running the SQL query.
  • Key Multiple

    Controls how many keys are used to create each query. This allows processing multiple keys at a time. You will need to construct your query such that it will handle multiple key values (example. where a ${key:=} will automatically use an ‘in’ clause to handle multiple keys). A value of 1 executes the query for each key. Values greater than 1 allow for huge performance gains. Make sure not to specify more keys than the database can support.
  • Fetch Size

    The number of rows to fetch from the database at a time. This can affect memory usage and performance and is only needed in special circumstances. Usually, this field is left blank. Different databases handle fetch size differently.

    • PostgreSQL: has no effect on the report performance. It is recommended to leave the default to 1000 unless you have a query with many columns. You can reduce the value to 100 or 10 with no penalty on performance.
    • Oracle: can greatly affect performance and memory usage. Performance is best with values of 1000 or more. However, if you have a query with very few rows and many columns, Oracle will try to create memory for 1000 rows, even if you only have one. In this case, it is recommended that you set the fetch size to the number of rows you expect to get from query.
  • Query Timeout

    Time in seconds to wait for the query to complete. Leave blank for default value.
  • Use Double

    Select the check box to convert all floating-point numeric values to Double objects instead of BigDecimal objects. This will save a lot of memory and network bandwidth at the cost of a slight loss of precision.
  • Query

    The data source and query to run against the data source.

    • Example using Keys: select * from well where uwi ${key:=:’}
    • Example using Tokens: select * from production where year = ${user_date,DATE,yyyy}

Did you find apk for android? You can find new Free Android Games and apps.