because of the interest we have in postgresql 15, my team and I would like to migrate to this new version. As we work with docker, I loaded the postgres:15 image instead of the old postgres:13 image and got it on my PC.
Now my problem is that I can't find a way to use Postgres:15 on my DataGrip IDE.
I can still write postgresql 14 code in DataGrip.
select version();
in a query console in DataGrip gets me version 15.1 version response but new commands such as MERGE can't be found by the IDE.
I found out after some research that the old version persisted in a terminal call of psql so i deleted the old cluster because they had the same port and name and now when i call psql in a terminal, I can write in postgresql 15.1 but still not on DataGrip.
There's a plan to implement it from 2023.1: https://youtrack.jetbrains.com/issue/DBE-16310
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 installed MariaDB and phpMyAdmin on my Synology at work and created a database. I was able to create the first fields with LO Base, which means that the JDBC-connector is working. The user hast % as location and I can edit everything from my machine with IntelliJ IDEA.
But: when I try to create a view with LO Base I get: The field names from 'database. Tables' could not be retrieved
I can see the data/rows in LO Base but I am not able to edit it. Which is possible in IDEA (add rows, modify content, etc.). I use the same credentials.
I do have the newest JDBC-driver/connector from the mysql-website and the connection-test worked. Is there a known issue with the latest release of base? I was able to do this in LO 4.X.
I use Ubuntu 16.04 on my laptop the synology OS is up to date, so as the packages.
Thanks in advance!
Just in case someone has the same problem: my database had underscores in the name. Removing them solved the issue.
When I add an Oracle Database as a Data Source to my project, the automatically generated code in the TableAdapter section is uses System.Data.OracleDataAdapter which is obsolete.
Following the documentation explains that you should use the third party Oracle software (ODAC). Given that the code is autogenerated, I am confused.
Am I missing something here?
Possible Solutions:
I could use .NET 3.5 for my Data Access Layer
Ignore the warnings
Manually Create Table Adapters
Something I am missing?
The solution is to use Oracle Developer Tools for Visual Studios. Add the Data Source in the same way as before (except the form now looks different as a result of the newly installed add on).
I am following book Getting started with oracle suite 11g R1 A Hands on tutorial.
I am using a bit more recent versions that recommended in book (because there is no place any more where I can download files recommended by book) and till now everything was OK.
Specifically I am using JDeveloper Studio Edition Version 11.1.1.5.0, Build JDEVADF_11.1.1.5.0_GENERIC_110409.0025.6013, SOA Composite Editor 11.1.1.5.0.01.74 and SOA Server PCBPEL_11.1.1.5.0_GENERIC_110418.1550.0174
while in book they suggest JDEVADF_11.1.1.1.0_GENERIC_090615.0017.5407. and SOA Composite Editor: 11.1.1.0.0.52.19 and SOA Server PCBPEL_11.1.1.1.0_GENERIC_090618.1440.5219.
Here comes the problem:
In book they instruct to do this
But when I try do do that, i get this (look similar to screenshot from book)
...and here comes the big difference...
..and especially after I click at magnifying glass...
After this point whatever I try I can't get to this:
Have a missed some step?
Or if the JDeveloper version are so much different how should I accomplish what they instruct to do? Or a problem is in a SOA suite or it's JDeveloper extension?
Up to this point all tests were passed, and everything was working as suggested in a book.
How should I resolve that problem?
Where could I get files that they advise to be used as Oracle is not offering them anymore for download?
(quotation from book)
Go to:
http://www.oracle.com/technology/products/soa/soasuite/index.html, and
download the following from SOA Suite 11g Release 1 (11.1.1.1.0) to
c:\stageSOA:
WebLogic Server:wls1031_win32.exe
Repository Creation Utility:ofm_rcu_win32_11.1.1.1.0_disk1_1of1.zip
SOA Suite:ofm_soa_generic_11.1.1.1.0_disk1_1of1.zip
JDeveloper Studio, base install: jdevstudio11111install.jar
Is there ANY tutorial or book which covers the most recent version of SOA Suite 12c altogether with JDeveloper and Database - so in short, updated version of their book? Especially if it covers SoreFrontDemo (or similar) application?
UPDATE: If I click here
and select that option than I have option to do this:
..and this...
and finally this - coud thisbe resolution to this problem?
UPDATE 2:
I found JDeveloper version jdevstudio11112install.jar and with it screenshots from book matches screen menus from that version of JDeveloper. Still it would be better if i could find version jdevstudio11111install.jar. I had to find and manually install soa-jdev-extension.zip because it is not avaiable with automatic update/install of extesnions (JDeveloper asks for support username and pass).
What I want to ask is how to get to following screens in JDeveloper jdevstudio11115install.jar or jdevstudio11117install.jar or who are still more- less officially supported.
If I could get there then I could set those parameters instructed by the book.
Is there ANY place where I could get jdevstudio11111install.jar as well as the following files from SOA Suite 11g Release 1(11.1.1.1.0):
WebLogic Server: wls1031_win32.exe
Repository Creation Utility: ofm_rcu_win32_11.1.1.1.0_disk1_1of1.zip
SOA Suite: ofm_soa_generic_11.1.1.1.0_disk1_1of1.zip
JDeveloper Studio, base install: jdevstudio11111install.jar
At this point:...
and here comes the big difference...
Click the Green + where it says Input - this will lead you to where you can choose the type.
The search-spyglass icon you were clicking on is where to SAVE the WSDL it will generate based on the XSD. You choose the XSD by clicking the Green +.
A GREAT book to learn SOA Suite is here.
Start with that and go through the tutorial at the back - takes you from XSD/WSDL to full SOA Suite impl in a few chapters.