It means that while on server when you use OFFSET, you must have a LIMIT clause as well, you can use OFFSET alone in SQL++ on mobile.
Thanks, so the correct docs should be:
| Feature | SQL++ for Couchbase Server | SQL++ for Mobile |
|---|---|---|
| LIMIT l OFFSET o | Does not allow OFFSET without LIMIT | Allows OFFSET without LIMIT |
In Table 1. Replication Retry Configuration Properties should be
- Set to
zeroone (1) to prevent any retry attempt
Setting ReplicatorConfiguration.pinnedServerCertificate in Example 6 and Example 19 both cast the certificate from TLSIdentity.certs[0] as X509Certificate, but pinnedServerCertificate expects a ByteArray (byte[] in Java).
@blake.meike should this be TLSIdentity.certs[0].encoded instead?
Ah, looks like 3.1 introduced ReplicatorConfiguration.setPinnedServerX509Certificate, deprecating the byte[] setPinnedServerCertificate. And ReplicatorConfiguration.newConfig() changed the type of pinnedServerCertificate to X509Certificate. So this is correct for 3.1, never mind on this one.
The docs still reference the deprecated removeChangeListener(ListenerToken) API. it’d be good to update this with the 3.1 ListenerToken.remove() API.
The replicator Using Kotlin Flows and LiveData code sample is missing.
gripe, gripe, gripe… 
Thanks. On it.
Another missing Flow sample. Seems like all the Flow sample links may be broken.
Certificate pinning Example 19 doesn’t use a wss URL like it needs to.
There’s conflicting info about the default delta sync state for peer-to-peer sync. Here it says:
Intra-Device replications automatically disable delta sync, whilst Peer-to-Peer replications automatically enable delta sync.
But here it says:
Optional delta-sync support is provided but is inactive by default.
Also here:
Delta sync replication is not enabled by default.
The .NET API reference docs links are returning 403 errors, all the ones I tried on this page at least.
It looks like the API docs themselves aren’t published for 3.1.1. 3.1.0 works, but only a main page for 3.1.1.
The “Importing a TLS identity” Example 6 is missing in the Android SDK docs.
Also, the “Create Self-Signed Cert” example is missing most of the code in both the Java and Android docs.
The “password authentication” example in the Android docs is showing nearly the entire sample code file contents.
The server (listener) must have
disableTLSsetfalseand have a ClientCertificateAuthenticator configured, or it will never ask for this client’s certificate.
Should reference ListenerCertificateAuthenticator instead of ClientCertificateAuthenticator.
This link (found here) is missing:
written to separate log files filtered by log level
Under File logging configuration, the second half of this line doesn’t belong here:
- log file path to the directory to store the log file Once this limit is exceeded a new log file is started.
These statements here:
this method will never be called if param level < this.level
this custom logger will not log an event with a log level < WARNING
seem to be contradicted by:
Here we set the custom logger with a level of ‘warning’. The custom logger is called with every log and may choose to filter it, using its configured level.
Maybe I’m reading it wrong, but would be good to clarify.
This page in the Swift and Objective-C docs has no content.
This is all great investigation, but is not something that we directly control so reporting it here is adding an extra middle step to actually getting the documents fixed. On each docs page there is a link called “Leave Additional Feedback?” that is usually located on the upper right hand side of the page. If you write this stuff using that link, that will open a ticket directly with the doc writing team. If this is something that you could do I think it would make this process a bit more efficient. It will also give you an actual ticket to look at to see what is happening with it!
Thanks @borrrden. It sounds like @blake.meike did create a ticket for the docs team. I figured I’d keep the feedback here in the same place for them to reference, since I don’t have a link to that ticket.
I finished going through most of the docs, so this was all the feedback I found up to this point. I’ll remember to use the feedback link to open a ticket if I find anything in the future.
There were quite a few other smaller things I didn’t even bother coming back to this thread to report, mostly typos here and there. It might be helpful for the team to check out my Kotlin Multiplatform library docs once I get it released soon.
I couldn’t find an issue opened by blake. I opened one - DOC-11433.
In the future, please use the “Leave Additional Feedback” link on the bottom right as it does open a ticket.