Jump to content
We've recently updated our Privacy Statement, available here ×

Tom C

Jaspersoft Staff
  • Posts

    453
  • Joined

  • Last visited

 Content Type 

Profiles

Forum

Events

Featured Visualizations

Knowledge Base

Documentation (PDF Downloads)

Blog

Documentation (Test Area)

Documentation

Dr. Jaspersoft Webinar Series

Downloads

Everything posted by Tom C

  1. User RequirementDue to the security policy and user information process restrictions by the DBA, our users are not "allowed to have user profile information in the jiuser table stored in any other media for any reason". This restriction could make it impossible to migrate user profiles using export/import utilities for the JasperReports® Server 7.5.1 to 7.9 upgrade. The Suggested ApproachIn JasperReports Server upgrade guide, there's a process to use js-upgrade-samedb shell script to upgrade two adjacent versions of the product. This upgrade keeps the existing repository content as is but simply updates the DB schema to reflect any changes for tables, columns, indice, and reference keys. The process consists of two parts: update the DB schema, and deploy the new JasperReports Server web application. Users can use a similar approach to upgrade their JasperReports Server from 7.5.1 to 7.9 as the following: If the profile database is managed by their DBA, users can ask him/her to run the following SQL scripts under buildomaticinstall_resourcessql{repo database} folder in the installation package: postgres=#\i upgrade-postgresql-7.5.0-7.8.0-pro.sql If users' DBA has granted access to the repo database to application users, then the users can configure default_master.properties file and run the following ANT script: cd \Jaspersoft\jasperreports-server-7.9.0\buildomatic js-ant upgrade-7.5-7.8-pro This will take care of the repo DB part of the upgrade from JasperReports Server 7.5 to 7.9. Note: There are no schema changes between 7.8 and 7.9 version of JasperReports Server repository therefore users do not need to run DB script for 7.8-7.9 upgrade. The JasperReports Server 7.9 js-upgrade-samedb script just carries out theme update and web application deployment which will be covered in the following steps. The application users can update repo with JasperReports Server 7.9.0 default theme by either run js-ant import-minimal-for-upgrade-pro or import the corresponding 7.9 default theme provided by Jaspersoft Tech Support. The application users can deploy JasperReports Server 7.9.0 using the installation script: js-ant deploy-webapp-pro TTC-20211130-2050825
  2. When deploying TIBCO JasperReports® Server v7.5+ on a server farmSharing the same repository database through load balancer, user need to make sure that each server node should have identical deployment in the following components: The entire jasperserver-pro web deployment folder under webapps directory; The keystore files (.jrsks and .jrsksp) in the user home directory; Any jar files needed by JasperReports Server in the web application server directory. For example, JDBC drivers for the JasperReports Server repository database are placed in the ..apache-tomcatlib folder. Last but not least, make sure to configure ehCache replication on each server node and use pinned sessions as required for JasperReports Server to function correctly due to its thin client architecture framework. References:https://community.jaspersoft.com/documentation/tibco-jasperreports-server-security-guide/v790/keys-during-installation https://community.jaspersoft.com/wiki/tibco-jasperreports-server-75-encryption-configuration-files https://community.jaspersoft.com/documentation/tibco-jasperreports-server-ultimate-guide/v790/sample-configurations https://community.jaspersoft.com/documentation/tibco-jasperreports-server-ultimate-guide/v790/session-management-and-failover TTC-20211130-2050825
  3. The ProblemUser has created a dashboard with an ad hoc view crosstab. When exporting this dashboard to a spreadsheet, the Excel only shows the summary level data without the detailed line items. The CauseUser must have collapsed the crosstab in the dashboard with summary data only before exporting the ad hoc view into an Excel output file. The SolutionUsers need to make sure the crosstab ad hoc view in the dashboard is not collapsed before any export operation, for "what you see is what you get". To prevent this from happening accidentally causing any confusion as in the case scenario, users can deploy ad hoc view REPORT in the dashboard therefore disabling the ad hoc view interactive feature to collapse/expand crosstab cells. Users however will have to contemplate the pros and cons of this feature limitation to decide whether to use view or report in the dashboard to meet the reporting requirement. TTC-20211130-2061700
  4. Tom C

    Queries

    <jasperReport xmlns="http://jasperreports.sourceforge.net/jasperreports" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jasperreports.sourceforge.net/jasperreports http://jasperreports.sourceforge.net/xsd/jasperreport.xsd" name="BlahBlahBlah" pageWidth="792" pageHeight="612" orientation="Landscape" columnWidth="752" leftMargin="20" rightMargin="20" topMargin="20" bottomMargin="20" isSummaryWithPageHeaderAndFooter="true" uuid="bbcb539b-1bc4-4aae-b4e0-xx123456dxyz">
  5. The Problem A user is getting the following error when importing a report unit into a new JasperReports Server (JRS) repository: ERROR Digester:1132 - End event threw exception java.lang.reflect.InvocationTargetException ............ Caused by: net.sf.jasperreports.engine.JRRuntimeException: No query executer factory registered for the ...... This report unit works perfectly in the JRS instance from which the exported repo content file was generated without any problem. The Cause This user uses their own custom SQL executor class to extend their Oracle PL/SQL function for additional processes before and after the query operations. This user is asking why js-import utility needs the custom class since it "is only applicable at report run time". JRS import utility process does make a minimum audition on resources for various reasons and this custom class method used in the report execution is indeed needed to pass the import audit to ensure the report unit is correctly deployed with all the integrated components. The Solution This user needs to add their custom component jar file containing the missing class to their new JRS deployment before running the import in order to migrate the reports unit successfully. For command line import utility, user needs to add the jar to: buildomaticconf_sourceieProlib For running the import in JRS web UI, user needs to add the jar to: jasperserver-proWEB-INFlib ================================================= TTC-20210831-2045704
  6. Tibco Jaspersoft has a new procedure for users to log Ideas for Jaspersoft products in the Jaspersoft Ideas Portal. When users has a support case issue which requires a feature enhancement to resolve, our suggestion is for user to file an enhancement request by themselves at the following web site: https://jaspersoftideas.tibco.com/ideas On navigating to the Ideas portal, users will see a list of ideas logged by customers as well as internal team members. Users can scroll through the list to get an idea of what enhancements are being requested by others. If feeling any idea is useful, users can vote for the idea by clicking on the Vote button. By clicking on the “Add a New Idea” button, it will take users to a form in which they can enter an idea for a new feature or enhancement. Enter the information in the fields to create a new Idea for the enhancement request. Your Idea: This is a required field. You will need to enter a short summary of your idea. Category: This is a required field. This refers to the product which the Idea refers to. For example, JasperReports Server, Jaspersoft Studio. Components: This is a required field. This refers to the component which the Idea refers to. For example, AdHoc, Domains, Report Viewer. Please add more details: This is a short description of the idea, please add as much detail as users' think will be useful to the team reading this. Users can also attach files. I need this: This is the priority field, it denotes how urgently users want their request to be implemented. Disclaimer: Though TIBCO Support strives to fulfill our users' needs, the actual timelines involved in processing the request might vary based on the complexity and feasibility. Tell us who you are: We require an official or personal email address so that we contact users if necessary. Disclaimer: To respond to our users' request, TIBCO Software Inc. and TIBCO affiliates (collectively "TIBCO") need to collect their email IDs. By providing this information, users are consenting to TIBCO processing this data and contacting you by email with the response related to the specific request. ---------------------------------------------------------------- Hope this helps to clarify the issue. ============================================ TTC-20210831-2043650
  7. The Question: User has deployed JasperReports Server (JRS) in a clustered server farm. Both server nodes are configured with the same amount of heap memory allocation, JAVA_OPTS="-Xms1024m -Xmx12288m". Each node has a different amount of RAM available. Is it Okay to have different heap memory allocation on each node to better utilize the available resource for JRS? The Answer: Users can certainly have different heap memory allocations on different server nodes to host JRS. Heap memory allocations for each server node do not have to be the same as long as it can serve primarily the reporting request on the data volumes by JRS running on that node. To clarify, the main considerations for JRS server farm deployment are the shared keystore files, the load balancer sticky/pinned session requirement, and ehcache replication between server nodes to keep their cached repo content in the instances in sync when sharing a repo database. ===================================================== TTC-20210831-2046954
  8. The Problem A user is upgrading/migrating their repository content from a JasperReports Server (JRS) version 7.5.1 deployment to a version 7.9.0 deployment using the command line js-export script. The import stops after importing few user profiles with the following error: Weak password Even with the failed import, this user is able to log into JRS 7.9.0 using the user credential that was shown in the import process right before the error occurred. The Cause JRS default configuration does not have any restriction on user password patterns and the regular expression default pattern ^.*$ matches any password. If a user customizes the password pattern with more restrictive requirements, such as minimum and maximum password length, using both uppercase and lowercase characters, and/or needing at least one number or special character, etc., any user password entered after the pattern change would reflect and meet those requirements. However, any existing password already created and stored in the user profile table in the repository will not be affected and users will be able to continue to use those "weak" passwords to log into the application successfully until they change their password. When migrating user profile data from one JRS deployment to another configured with the more restrictive password patterns, those users with the "weak" passwords will fail the import with the above error. IMPORTANT: For other potential causes of the 'Weak Password' error please see this article: Command Line export of users to a catalog is causing the import of the catalog to fail with "Weak password" error The Solution To get the repository content migration successful with user profile data, our users must ensure all user passwords meet the password pattern for the user authority service before exporting its content for the migration. This involves requesting legacy users to change their password from the JRS User Profile web UI meeting the new password pattern rules. It is not always possible, however, to ensure the changes would take place in a timely manner within the migration timeline and schedule, especially if the users community is external and population is large. In such a case, users should use the standard password pattern configuration for their command line import process to proceed without the weak password restrictions. The configuration file involved for the command line import is the "applicationContext.xml" file under the buildomaticconf_sourceiePro directory. Users can restore the default setting to avoid this import error. <property name="allowedPasswordPattern" value="^.*$"/> ReferencesFor other potential causes of the 'Weak Password' error please see this article: Command Line export of users to a catalog is causing the import of the catalog to fail with "Weak password" error ===================================================== TTC-20210831-2046296
  9. FYI....... https://community.jaspersoft.com/wiki/tibco-jasperreports-server-780-installation-using-windows-binary-installer-might-have-problem
  10. 1) You need to make perfect alignment for all fields in vertical direction; 2) Do not overlap fields.
  11. With all due respect, the sample is not a fake report but the content of a "correct"/working/tested report template jrxml file. You just need a (any) PostgreSQL data source to test run it in Jaspersoft Studio (JSS) and produce the result as shown in my posting. The intention here is to show users how this can be accomplished using JasperReports engine (JRL) to meet your particular requirement. Please refer to Jaspoersoft Studio User Guide to learn how the product is supposed to work in general. https://community.jaspersoft.com/documentation/tibco-jaspersoft-studio-user-guide/v790/getting-started-jaspersoft-studio You can also review many of Jaspersoft studio tutorial videos from the user community on YouTube to get yourself familiar with the features and capabilities of our product. Hope this provides enough guidance level information and helps to steer you into the right direction.
  12. https://community.jaspersoft.com/documentation/tibco-jaspersoft-studio-user-guide/v790/working-charts
  13. Users can experience unused space problems in the report layout when the "RemoveLineWhenBlank" property is used in the report design to suppress optional report elements. In the following sample report, we can observe that after record 21, there is a lot of free space left in the report output that could easily fit a few more records on the page. Instead, the space is not used and those records are displayed in the following page. We have filed a report to address this defect that relying on "RemoveLineWhenBlank" property to shrink the band height can cause the JasperReports engine (JRL) to miscalculate the remaining space on a page. The internal reference number for the bug report is JRL-1640. To work around this problem, users can put the optional report element in the second detail band and use band "print when condition" to determine whether the band will be called to display the element. This will avoid relying on RemoveLineWhenBlank property to shrink the band height causing the miscalculation. Sample report template:<?xml version="1.0" encoding="UTF-8"?> <!-- Created with Jaspersoft Studio version 7.9.0.final using JasperReports Library version 6.16.0-48579d909b7943b64690c65c71e07e0b80981928 --> <jasperReport xmlns="http://jasperreports.sourceforge.net/jasperreports" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jasperreports.sourceforge.net/jasperreports http://jasperreports.sourceforge.net/xsd/jasperreport.xsd" name="results" pageWidth="595" pageHeight="842" columnWidth="595" leftMargin="0" rightMargin="0" topMargin="0" bottomMargin="0" isFloatColumnFooter="true" uuid="e731fea9-a92e-4fae-b620-244bb0584a33"> <property name="com.jaspersoft.studio.data.defaultdataadapter" value="JRSrepo"/> <property name="com.jaspersoft.studio.data.sql.tables" value=""/> <parameter name="displayRowNumber" class="java.lang.Integer"> <defaultValueExpression><![CDATA[20]]></defaultValueExpression> </parameter> <queryString> <![CDATA[with reportdata as (select i, 'text '||i as text from generate_series(1, 50) i) select text, (case when i = $P{displayRowNumber} then 'Pretend Image' else '' end) as image from reportdata]]> </queryString> <field name="text" class="java.lang.String"> <property name="com.jaspersoft.studio.field.name" value="text"/> <property name="com.jaspersoft.studio.field.label" value="text"/> </field> <field name="image" class="java.lang.String"> <property name="com.jaspersoft.studio.field.name" value="image"/> <property name="com.jaspersoft.studio.field.label" value="image"/> </field> <detail> <band height="29" splitType="Stretch"> <textField isBlankWhenNull="true"> <reportElement mode="Opaque" x="0" y="0" width="595" height="29" isRemoveLineWhenBlank="true" backcolor="#FFFF00" uuid="64716bd8-b508-4caf-bd5f-16e81c10a80b"/> <box padding="0"> <pen lineWidth="1.25" lineStyle="Solid" lineColor="#030303"/> </box> <textElement> <font fontName="DejaVu Sans" isBold="true"/> <paragraph lineSpacingSize="0.0"/> </textElement> <textFieldExpression><![CDATA[$F{text}]]></textFieldExpression> </textField> </band> <band height="100"> <printWhenExpression><![CDATA[!"".equals($F{image})]]></printWhenExpression> <textField> <reportElement mode="Opaque" x="0" y="0" width="190" height="100" backcolor="#99FF33" uuid="9e150bf6-7e71-4997-b199-cabddb620bf7"> <property name="com.jaspersoft.studio.unit.height" value="px"/> <property name="com.jaspersoft.studio.unit.x" value="px"/> <property name="com.jaspersoft.studio.unit.y" value="px"/> </reportElement> <textFieldExpression><![CDATA[$F{image}]]></textFieldExpression> </textField> </band> </detail> </jasperReport> Report output: =================================================================== TTC-20210604
  14. JasperReports Server commercial edition available features: – Ad Hoc Designer– Analysis/OLAP– Audit– Dashboard– Fusion Chart– Multitenancy
  15. This looks like a defect when JasperReports engine (JRL) calculates the remaining space on a page involving the RemoveLineWhenBlank property. The work around is to put your image in the second detail band and use band print when condition to determine whether the band will be called to display the image. This will avoid relying on RemoveLineWhenBlank property to shrink the band height causing the miscalculation.
  16. You can use a report list element to lay out cities horizontally. See sample report: Report data: Simple report layout: Report output: Report design template (JRXML file): <?xml version="1.0" encoding="UTF-8"?><!-- Created with Jaspersoft Studio version 7.9.0.final using JasperReports Library version 6.16.0-48579d909b7943b64690c65c71e07e0b80981928 --><jasperReport xmlns="http://jasperreports.sourceforge.net/jasperreports" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jasperreports.sourceforge.net/jasperreports http://jasperreports.sourceforge.net/xsd/jasperreport.xsd" name="demo-20210603" pageWidth="612" pageHeight="792" columnWidth="555" leftMargin="20" rightMargin="20" topMargin="20" bottomMargin="20" uuid="3e4d9a69-d315-4243-ad30-8f6cef2f29ce"> <property name="com.jaspersoft.studio.data.sql.tables" value=""/> <property name="com.jaspersoft.studio.data.defaultdataadapter" value="JRSrepo"/> <property name="com.jaspersoft.studio.property.dataset.dialog.DatasetDialog.sash.w1" value="338"/> <property name="com.jaspersoft.studio.property.dataset.dialog.DatasetDialog.sash.w2" value="651"/> <property name="com.jaspersoft.studio.data.sql.SQLQueryDesigner.sash.w1" value="473"/> <property name="com.jaspersoft.studio.data.sql.SQLQueryDesigner.sash.w2" value="526"/> <subDataset name="Dataset1" uuid="fc1c4348-9a3a-42b2-a750-597914f2db75"> <property name="com.jaspersoft.studio.data.sql.tables" value=""/> <property name="com.jaspersoft.studio.data.defaultdataadapter" value="JRSrepo"/> <parameter name="name" class="java.lang.String"> <defaultValueExpression><![CDATA["Mr A"]]></defaultValueExpression> </parameter> <queryString language="SQL"> <![CDATA[select city from (select * from (values ('Mr A','City 1'),('Mr A','City 2'),('Mr A','City 3'),('Mr A','City 4'),('Mr A','City 5'),('Mr A','City 6'),('Mr B','City 1'),('Mr B','City 2'),('Mr B','City 3')) as t (Name,city) order by 1, 2) as reportdatawhere name = $P{name} order by city]]> </queryString> <field name="city" class="java.lang.String"> <property name="com.jaspersoft.studio.field.name" value="city"/> <property name="com.jaspersoft.studio.field.label" value="city"/> </field> </subDataset> <queryString language="SQL"> <![CDATA[select name from (select * from (values ('Mr A','City 1'),('Mr A','City 2'),('Mr A','City 3'),('Mr A','City 4'),('Mr A','City 5'),('Mr A','City 6'),('Mr B','City 1'),('Mr B','City 2'),('Mr B','City 3')) as t (Name,city) order by 1, 2) as reportdatagroup by name]]> </queryString> <field name="name" class="java.lang.String"> <property name="com.jaspersoft.studio.field.name" value="name"/> <property name="com.jaspersoft.studio.field.label" value="name"/> </field> <detail> <band height="30" splitType="Stretch"> <textField> <reportElement x="0" y="0" width="100" height="30" uuid="c18292b9-fff5-4867-b0c6-2d10f095338e"/> <textFieldExpression><![CDATA[$F{name}]]></textFieldExpression> </textField> <componentElement> <reportElement x="100" y="0" width="400" height="30" uuid="103320d3-4fd6-4d03-b189-74d441bb2e3f"> <property name="com.jaspersoft.studio.unit.width" value="px"/> <property name="com.jaspersoft.studio.unit.CONTENTS.width" value="px"/> </reportElement> <jr:list xmlns:jr="http://jasperreports.sourceforge.net/jasperreports/components" xsi:schemaLocation="http://jasperreports.sourceforge.net/jasperreports/components http://jasperreports.sourceforge.net/xsd/components.xsd" printOrder="Horizontal"> <datasetRun subDataset="Dataset1" uuid="4d4c98c6-5416-4786-a6d6-2b0fcc4a0926"> <datasetParameter name="name"> <datasetParameterExpression><![CDATA[$F{name}]]></datasetParameterExpression> </datasetParameter> <connectionExpression><![CDATA[$P{REPORT_CONNECTION}]]></connectionExpression> </datasetRun> <jr:listContents height="30" width="100"> <textField> <reportElement x="0" y="0" width="100" height="30" uuid="4a917ea1-6b17-4ccc-a722-6c0a9b1e3dae"/> <textFieldExpression><![CDATA[$F{city}]]></textFieldExpression> </textField> </jr:listContents> </jr:list> </componentElement> </band> </detail></jasperReport>
  17. Try "remove line when blank" setting for the image properties.
  18. The current release version for the JRS community edition is 7.8. The 7.9 version is primarily for JRIO At-Scale release which does not have a lot of JRS features in the open source (community) version. We will have a new JRS product release for both editions (commercial and community) in this fall of 2021.
  19. You can create a group based on $F{ordnum} but do not need to add group header and group footer (heights are zero for those bands). Just make sure to select "Start New Page" for the group header property. The screenshots are from a Jaspersoft Studio product (JSS) but this feature should work for iReport as well (iReport is no longer supported by Tibco Jaspersoft). Case in point, you do not need the group header to be visible to trigger the new page class method in JasperReports engine (JRL) when rendering a report output. <?xml version="1.0" encoding="UTF-8"?><!-- Created with Jaspersoft Studio version 7.9.0.final using JasperReports Library version 6.16.0-48579d909b7943b64690c65c71e07e0b80981928 --><jasperReport xmlns="http://jasperreports.sourceforge.net/jasperreports" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jasperreports.sourceforge.net/jasperreports http://jasperreports.sourceforge.net/xsd/jasperreport.xsd" name="demo4brandon" pageWidth="612" pageHeight="792" columnWidth="555" leftMargin="20" rightMargin="20" topMargin="20" bottomMargin="20" uuid="b51c190a-e11f-4fdc-9f2a-937ed1d5efcd"> <property name="com.jaspersoft.studio.data.defaultdataadapter" value="Sugarcrm"/> <property name="com.jaspersoft.studio.data.sql.tables" value=""/> <queryString> <![CDATA[select orderid||'' as ordnum from orders limit 3]]> </queryString> <field name="ordnum" class="java.lang.String"> <property name="com.jaspersoft.studio.field.name" value="ordnum"/> <property name="com.jaspersoft.studio.field.label" value="ordnum"/> </field> <group name="Order" isStartNewPage="true"> <groupExpression><![CDATA[$F{ordnum}]]></groupExpression> </group> <columnHeader> <band height="35" splitType="Stretch"> <property name="com.jaspersoft.studio.unit.height" value="px"/> <staticText> <reportElement x="0" y="0" width="180" height="30" uuid="1884c8ac-0b3c-4bdf-9eb0-741b527be444"> <property name="com.jaspersoft.studio.spreadsheet.connectionID" value="644491ef-a4e2-4f9b-81ce-54b081f3728e"/> </reportElement> <text><![CDATA[ordnum]]></text> </staticText> </band> </columnHeader> <detail> <band height="300" splitType="Stretch"> <property name="com.jaspersoft.studio.unit.height" value="px"/> <textField> <reportElement x="0" y="0" width="180" height="30" uuid="33a37ffd-051f-4383-a557-4bbfbcab3059"> <property name="com.jaspersoft.studio.spreadsheet.connectionID" value="644491ef-a4e2-4f9b-81ce-54b081f3728e"/> </reportElement> <textFieldExpression><![CDATA[$F{ordnum}]]></textFieldExpression> </textField> <staticText> <reportElement mode="Opaque" x="80" y="40" width="482" height="250" forecolor="#339900" backcolor="#FFFF33" uuid="882de33a-5705-46c4-a5f9-213b31a83246"/> <box> <topPen lineWidth="1.0"/> <leftPen lineWidth="1.0"/> <bottomPen lineWidth="1.0"/> <rightPen lineWidth="1.0"/> </box> <textElement textAlignment="Center" verticalAlignment="Middle"> <font size="26"/> </textElement> <text><![CDATA[Order Details]]></text> </staticText> </band> </detail></jasperReport>
  20. Your report template looks strange. Refer to the green colored element - Are you using an image to display report content? How are those parameters getting into the template? Are you superimposing them on top of the image? Refer to orange colored element - What we need to make sure is the input control unit id matches the report parameter name in the template (you need to expand the parameter list and see the names).
  21. Check the Page and Size Handlings settings in printer properties and experiment with different one to see if the label can be correctly aligned in Zebra ZT230 print.
  22. Custom calculations during report generation - if the calculation is simple, you can use in line Java expression and ternary operator in a report variable to meet your requirement. The tricky part is the evaluation time if your calculation is iteration specific across several rows. In such a case, scriptlet can help but you still need to put the call in the correct report location to get the information that you need. You can also rely on sub components (sub report, list, etc.) to conduct the calculation to avoid coding and implementation hassle with the scriptlet approach. In summary, it is all depending upon what you need to determine the simplest approach to meet your reporting requirement.
  23. For week range report - You need to break your data into five items based on the date range then display them horizontally using a list element. Something like: 1) Main report query gives the unique work/compaings record 2) Use list element to get the details of those work/compaings record into five rows then lay them out horizontally. The subdataset feeding the list could be something like: with workdata as (select * from your report_table where work_compaings = $P{work_compaigns})select 1 as week, * from workdata where {week is in week 1 range}union allselect 2 as week, * from workdata where {week is in week 2 range}union allselect 3 as week, * from workdata where {week is in week 3 range}union allselect 4 as week, * from workdata where {week is in week 4 range}union allselect 5 as week, * from workdata where {week is in week 5 range}[/code]
  24. One data source and 3 queries - Assuming those three queries produce identicle meta data result set, you can combine them together to product one result set: query1unionquery2unionquery3[/code]
×
×
  • Create New...