There are different app versions such as 5.1.2, 5.1.5.6, 6.7, 8.1.2, etc. I want to select all the records with app version > 5.1, however I cannot do so using below code.
The below code obviously throws error:
select * from db1
where platform = 'Android'
and clientversion > 5.1
Related
BIRT 431; Oracle 12c
IBM Maximo Asset Management 7.6.1.2 — only supports BIRT 431
I want to preview my BIRT reports (by connecting from BIRT to the Maximo database).
BIRT 431 requires Java 7. However, the latest version of JDBC for Oracle requires Java 8 (older drivers won't connect to the database).
If that's correct, then how can I preview BIRT reports if BIRT 431 doesn't support any functioning JDBC drivers?
A colleague provided this solution. I haven't been able to test it yet.
Use the latest available version of the jdbc driver for Oracle designed for Java 7:
Oracle Database 12.1.0.1 JDBC Driver & UCP Downloads --> ojdbc7.jar
In order to get preview features working for Eclipse BIRT 4.3.1 the following steps need to be taken:
Be sure that the version of Java being used for Eclipse is version 7. If it isn’t change it to version 7 as the preview feature will not work with 8.
Review chapter 2 in the attached document.
Save the attached file (ojdbc7.jar.txt) to the folder eclipse\plugins\org.eclipse.birt.report.viewer_4.3.1.v201309171028\birt\WEB-INF\lib below your base eclipse installation folder. Rename the file removing the “.txt”.
Create a copy of the file and change the extension from “.jar” to “.zip”.
Extract the contents of the zip file to eclipse\plugins\org.eclipse.birt.report.viewer_4.3.1.v201309171028\birt\WEB-INF\classes
Confirm Eclipse configuration as per the documentation from point 2.
Test with a report to confirmation functionality.
If there is an issue with the built in tool for previewing report output you may need to configure Eclipse to use a web browser instead.
In Eclipse use Window -> Preferences -> Report Design -> Preview.
Check the option “Always use external browsers.”
Click on the Web Browser link.
Click on the “Use external web browser” radio button and check “Default system web browser” or the browser of your choice if it appears in the list.
Related:
Maximo76_Designer431_Report Development Guide_Rev8.pdf
I recently upgraded Microsoft.Bot.Builder from version 3.8.0 to Version 4.2.2 (latest stable). Since then, everything got messed up. None of the Luis namespaces are getting resolved. For e.g., in Dialogs, I had below code:
[LuisModel("<KEY>", "<KEU>")]
public class TestDialog : LuisDialog<object>
{
}
but after upgrade, LuisModel does not resolve. I also added "Microsoft.Bot.Builder.AI.Luis" but it does not help!
The Bot Builder SDK was re-written between versions 3 and 4. There are many breaking changes. One of which is that there is no longer a LUISDialog. The V3 SDK is still maintained and supported, with the most recent version as of 2.25.2019 being https://www.nuget.org/packages/Microsoft.Bot.Builder/3.20.1
Some guidance for converting from V3 to V4 can be found here: https://learn.microsoft.com/en-us/azure/bot-service/migration/migration-about
when deploy my Joomla Component I put in an Update File for the Database. Even if there are no changes for the Database. Is this neccessary?
AND: What are the contents? Do I have to put only these SQL-Statements for the Changes from Version 3 to Version 4 or must there be also the changes from Version 1 and Version 2?
Best Regards
DreiBaer
I've done some tests and it doesn't look like you need a SQL update file for a version of your component which doesn't need to make any database changes. However, this may not have always been the case in older Joomla version, see below.
When you install your component for on a Joomla site which doesn't already have a version of your component, the only sql file which is run is the one referenced in the install node of your manifest file. The file may be something like sql/install.mysql.utf8.sql.
So long as the site doesn't have any version of your component, then even if you are installing a later version eg, 2.3.1, and this later version does have some SQL update files, those files will not be executed, only the install file for this version (2.3.1). However in such a situation, whist the SQL update files are not executed, their version numbers are parsed and the greatest version number is stored against the component in Joomla's schemas table. If for example version 2.3.1 of your component contained the SQL update files 0.0.1.sql, 1.0.1.sql, 1.2.1.sql and 2.0.4.sql, then on first installation of this component, the schemas table will have a version_id of 2.0.4.
When updating a component the install SQL file is not executed. Joomla checks the schema version of the installed component and then executes, in order, each SQL update file which has a schema version number greater than the installed schema version number. For example if you have your component installed and it has a schema version of 1.5.2 and you're update contains the SQL update files 1.4.1, 1.5.0, 1.5.2, 1.5.19 and 1.6.0, then only SQL scripts 1.5.19 and 1.6.0 are executed and in that order.
If you install a component for the first time and it has no update file, then the schema table contains a record with a blank version_id field. If you then update that component with a version which does contain SQL update files, then the original schema version is calculated as zero and all update files are executed.
Together what this means, is that for each version of your component, the SQL install file must have all the necessary SQL statements to get the database into the correct state for your component version. On installation, even installation of a later version of your component, no updates will run, so the only SQL you can use to manipulate the database is the SQL in the install file.
So that you component can be upgraded correctly, you must have SQL update files which can take whatever the installed version is up to the version you are trying to update to. If for example an administrator has fallen behind in updating your component, and they have version 1.0.0 installed and want to update directly to your latest version, say 4.0.0, then version 4.0.0 needs to contain the updates from 1 to 2, 2 to 3, 3 to 4 and any subversions between.
There is this old article from Joomla's documentation which discusses exactly the questions you're asking, however its outdated (for version 2.5) and I think the information isn't accurate any longer.
This article says that it is necessary to have blank SQL update files for versions which don't have any SQL updates, otherwise subsequent updates with SQL update files will not be executed, however I've tested this and it doesn't seem to be a problem. This may have been true in older versions of Joomla, but is not true as of the version I tested on (3.5.7).
Its probably best practice to stick to the convention described in the documentation - including the empty SQL update files as it can't hurt, and as the behavior I found in testing is undocumented it could change without warning in the future.
The documentation also says that component version needs to match the update SQL file version, but again I found that this is no longer correct. You can use a SQL schema versioning which is totally independent from the component versioning without any problems. However, again its probably a good idea to keep schema and component version in step with each other - I can't think of a good reason why you wouldn't do this.
I'm trying to do a simple thing: add a column with datatype ENUM in a MySQL Workbench model. The problem is, the choice is just not there. I cannot select 'ENUM'.
If I open an old project or create a new one in the same Workbench I do have the choice, so it seems to be a setting, but I don't have a clue where to look. It's not some SQL thing, because an export and import (reverse engineer) in a new model also shows the ENUM columns.
To be clear: it is NOT that I'm typing something like enum(choice,choice2) and so generating a syntax error, the dropdown has no ENUM.
Tested on:
Mysql Workbench version: 5.2.47 CE (revision 10398) on Windows 7
Mysql Workbench version: 5.2.40 (revision 8790) on Ubuntu 13.04
Mysql Workbench version: 6.0 community (build 6.0.3.11035) (BETA) on Windows 7
Settings for all projects are the same ('default'), in my case
Default target mysql version: 5.5
Storage engine: InnoDB
SQL_MODE to be used: TRADITIONAL,ALLOW_INVALID_DATES
There seem to be several missing types, at least:
BIT
ENUM()
SET()
I consider this now an official "bug" and therefore a real solution will not be forthcoming.
Only thing you can do is start a new model, and re-create all your work there.
I see the following problems using ChildBrowser plugin in ios phonegap.
My mapping file is updated with ChildBrowserCommand and I allowed external hosts to *
My Environment
Xcode 4.5
ios 6
Phonegap 2.0
2012-09-26 12:36:07.419 HelloWorld2[2566:c07] ERROR: Plugin 'ChildBrowserCommand' not found, or is not a CDVPlugin. Check your plugin mapping in Cordova.plist.
2012-09-26 12:36:07.420 HelloWorld2[2566:c07] FAILED pluginJSON = [null,"ChildBrowserCommand","
showWebPage",["http://google.com"]]
They released recently v2.1, I suggest you giving it a try since now they are supposed to officially support ChildBrowser plugin