Below mentioned problem occurred while migrating mongodb from 2.x version to 3.x, where QUERYOPTION_AWAITDATA was used on a non-tailable cursor.
Problem statement:
In the earlier version i.e, in 2.11.4 version of MongoDB-Java driver , we were allowed to use QUERYOPTION_AWAITDATA on a non-Tailable cursor.
But in version 3.2 of MongoDB-Java driver, we are only allowed to use QUERYOPTION_AWAITDATA on a Tailable cursor.
Question:
What difference was it making by adding QUERYOPTION_AWAITDATA to an non-Tailable cursor in 2.11.4.
If there is a reason for having QUERYOPTION_AWAITDATA for an non-Tailable cursor, then how can this be addressed in 3.2 version of mongodb-java Drvier.?
Is QUERYOPTION_AWAITDATA necessary for a non-Tailable cursor.
No, it's not necessary. I'd consider it a bug that 2.x allows you to set that on a non-tailable cursor and that 3.x just fixed the glitch.
Related
I am going to maintain a rails application locally on Mac M1 based computer.
OS Version: Monterey 12.1
Ruby version 2.6.6
Rails version 4.2.11
I am getting this error and can't figure out what is actually causing this error to raise.
The error logged in console:
/Users/shimolkhan/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/dry-validation-0.13.3/lib/dry/validation/schema/class_interface.rb:8:in `<module:Validation>' [dry-configurable] default value as positional argument to settings is deprecated and will be removed in the next major version Provide a `default:` keyword argument instead
Please help me. Thanks in advance.
It looks like there may be a small incompatibility between the versions of dry-validation and dry-configurable that you are running.
This deprecation was introduced into dry-configurable 0.13.0 (the latest version) recently here:
Changelog Pull Request
Yet according to the fragment you pasted, you're running dry-validation 0.13.3, which is almost 3 years old.
I'd suggest updating your version of dry-validation and perhaps all dry gems.
I upgraded to php7.4 on my dev box and am receiving a lot of deprecated errors with Propel 1.7.2. I see there is a closed thread in the support channel indicating fixes are in master, but they sure haven't made it to Propel 1.7.3 at http://propelorm.org/Propel/download.html. Does anyone know if/when the Propel folks are going to release a 1.7.x that is compatible with php74 (php 7.4)?
I wouldn't expeced to much from propel. The Project is more or less dead as of March 21.
As of their official github-page propel1 is outdated and unmaintained. See: https://github.com/propelorm/Propel
Current stable (and outdated and unmaintained) version of Propel -
Please use v2 https://github.com/propelorm/Propel2
Propel2 on the other hand is still in alpha. See: http://propelorm.org/download.html
Note: The version 2 of Propel is still under development. Please visit
http://propelorm.org/Propel/ if you want to use a stable version.
There is also Propel3. Which is not even in alpha yet. See: https://github.com/propelorm/Propel3
Propel3 is an open-source Object-Relational Mapping (ORM) for modern
PHP 7.1+. Version 3 of Propel ORM replaces Propel2, which is not
maintained anymore.
Maybe also see the discussion here: https://github.com/propelorm/Propel3/issues/92
I have Oracle version 12.2.0.1.0
We have generic script which create sequence that need to be reuse for different objects (by renaming sequence name):
CREATE SEQUENCE NAME_SEQ MINVALUE 1 MAXVALUE 999999999
INCREMENT BY 1 START WITH 100 CACHE 200 NOORDER NOCYCLE NOPARTITION ;
This script isn't working with below error until I remove NOPARTITION :
ORA-00933: SQL command not properly ended
I found in AskTom that the NOPARTITION is not supported in 12.2
there's been various of things in previous versions of the database that are no longer relevant/supported
Why it's not supported and/or what is the replacement of this feature ?
If there's no replacement can you state why this feature shouldn't be used?
The (no)partition option for sequences was never documented. And thus never supported.
There was a bug in 12.1 which exposed this via dbms_metadata. It no longer happens in 12.2
Undocumented features can (and as this proves) do change without warning. Using them is strictly at your own risk.
If you do a dbms_metadata.get_ddl from database version 12.1 and want to use it in 12.2 then a NOPARTITION is supplied. Now we have to remove it.
In previous versions of SonarQube we had a property that allowed setting the context root sonar.web.context however after a recent update, this does not appear work anymore. Is there an alternative method of performing this function?
Seems like they have decided to just drop the capability on 5.4 https://jira.sonarsource.com/browse/SONAR-7122
But may be reintroduced in 5.5 https://jira.sonarsource.com/browse/SONAR-7494 so I guess I had downgraded Sonar to 5.3. That way my reverse-proxy-auth-sonar-plugin that I for my installation still functions correctly.
You can upgrade to 5.6.3 LTS http://docs.sonarqube.org/display/SONAR/Upgrading, the capability was included again from 5.5 on.
I have installed ruby 2.1.5 version and want to downgrade it to 1.9.3 to avoid "DL is deprecated, please use Fiddle in windows". I have tried rmv function, but it is not working and also tell me how to remove older versions.
So what's the issue ? Does migration complete ? If you mind just for the warning about DL being deprecated, downgrading to already unsupported Ruby version sounds ridiculous.
This may be just quite unharmful notice for developers to start using newer C-extension interface, while functionality is kept unaffected.