questdb 1.2.0__tar.gz → 2.0.1__tar.gz

questdb-2.0.1/CHANGELOG.rst

@@ -0,0 +1,325 @@
+.. _changelog:
+
+Changelog
+=========
+
+2.0.1 (2024-03-22)
+------------------
+
+Patch release with bug fixes, no API changes and some documentation tweaks.
+
+Bug fixes
+~~~~~~~~~
+* Fixed a bug where an internal "last flushed" timestamp used
+  by ``auto_flush_interval`` wasn't updated correctly causing the auto-flush
+  logic to trigger after each row.
+
+* Removed two unnecessary debugging ``print()`` statements that were
+  accidentally left in the code in ``Sender.from_conf()`` and
+  ``Sender.from_env()``.
+
+Documentation
+~~~~~~~~~~~~~
+* Introduced the ability to optionally install ``pandas`` and ``pyarrow`` via
+  ``python3 -m pip install -U questdb[dataframe]`` and updated the documentation
+  to reflect this.
+
+
+2.0.0 (2024-03-19)
+------------------
+
+This is a major release with new features and breaking changes.
+
+Features
+~~~~~~~~
+
+* Support for ILP over HTTP. The sender can now send data to QuestDB via HTTP
+  instead of TCP. This provides error feedback from the server and new features.
+
+  .. code-block:: python
+
+    conf = 'http::addr=localhost:9000;'
+    with Sender.from_conf(conf) as sender:
+        sender.row(...)
+        sender.dataframe(...)
+
+        # Will raise `IngressError` if there is an error from the server.
+        sender.flush()
+
+* New configuration string construction. The sender can now be also constructed
+  from a :ref:`configuration string <sender_conf>` in addition to the
+  constructor arguments.
+  This allows for more flexible configuration and is the recommended way to
+  construct a sender.
+  The same string can also be loaded from the ``QDB_CLIENT_CONF`` environment
+  variable.
+  The constructor arguments have been updated and some options have changed.
+
+* Explicit transaction support over HTTP. A set of rows for a single table can
+  now be committed via the sender transactionally. You can do this using a
+  ``with sender.transaction('table_name') as txn:`` block.
+
+  .. code-block:: python
+
+    conf = 'http::addr=localhost:9000;'
+    with Sender.from_conf(conf) as sender:
+        with sender.transaction('test_table') as txn:
+            # Same arguments as the sender methods, minus the table name.
+            txn.row(...)
+            txn.dataframe(...)
+
+* A number of documentation improvements.
+
+
+Breaking Changes
+~~~~~~~~~~~~~~~~
+
+* New ``protocol`` parameter in the
+  :ref:`Sender <sender_programmatic_construction>` constructor.
+
+  In previous version the protocol was always TCP.
+  In this new version you must specify the protocol explicitly.
+
+* New auto-flush defaults. In previous versions
+  :ref:`auto-flushing <sender_auto_flush>` was enabled by
+  default and triggered by a maximum buffer size. In this new version
+  auto-flushing is enabled by row count (600 rows by default) and interval
+  (1 second by default), while auto-flushing by buffer size is disabled by
+  default.
+
+  The old behaviour can be still be achieved by tweaking the auto-flush
+  settings.
+  
+  .. list-table::
+    :header-rows: 1
+
+    * - Setting
+      - Old default
+      - New default
+    * - **auto_flush_rows**
+      - off
+      - 600
+    * - **auto_flush_interval**
+      - off
+      - 1000
+    * - **auto_flush_bytes**
+      - 64512
+      - off
+
+* The ``at=..`` argument of :func:`row <questdb.ingress.Sender.row>` and
+  :func:`dataframe <questdb.ingress.Sender.dataframe>` methods is now mandatory.
+  Omitting it would previously use a server-generated timestamp for the row.
+  Now if you want a server generated timestamp, you can pass the :ref:`ServerTimestamp <sender_server_timestamp>`
+  singleton to this parameter. _The ``ServerTimestamp`` behaviour is considered legacy._
+
+* The ``auth=(u, t, x, y)`` argument of the ``Sender`` constructor has now been
+  broken up into multiple arguments: ``username``, ``token``, ``token_x``, ``token_y``.
+
+* The ``tls`` argument of the ``Sender`` constructor has been removed and
+  replaced with the ``protocol`` argument. Use ``Protocol.Tcps``
+  (or ``Protocol.Https``) to enable TLS.
+  The ``tls`` values have been moved to new ``tls_ca`` and ``tls_roots``
+  :ref:`configuration settings <sender_conf_tls>`.
+
+* The ``net_interface`` argument of the ``Sender`` constructor has been renamed
+  to ``bind_interface`` and is now only available for TCP connections.
+
+The following example shows how to migrate to the new API.
+
+**Old questdb 1.x code**
+
+.. code-block:: python
+
+    from questdb.ingress import Sender
+
+    auth = (
+        'testUser1', 
+        '5UjEMuA0Pj5pjK8a-fa24dyIf-Es5mYny3oE_Wmus48',
+        'token_x=fLKYEaoEb9lrn3nkwLDA-M_xnuFOdSt9y0Z7_vWSHLU',
+        'token_y=Dt5tbS1dEDMSYfym3fgMv0B99szno-dFc1rYF9t0aac')
+    with Sender('localhost', 9009, auth=auth, tls=True) as sender:
+        sender.row(
+            'test_table',
+            symbols={'sym': 'AAPL'},
+            columns={'price': 100.0})  # `at=None` was defaulted for server time
+
+**Equivalent questdb 2.x code**
+
+.. code-block:: python
+
+    from questdb.ingress import Sender, Protocol, ServerTimestamp
+
+    sender = Sender(
+        Protocol.Tcps,
+        'localhost',
+        9009,
+        username='testUser1',
+        token='5UjEMuA0Pj5pjK8a-fa24dyIf-Es5mYny3oE_Wmus48',
+        token_x='token_x=fLKYEaoEb9lrn3nkwLDA-M_xnuFOdSt9y0Z7_vWSHLU',
+        token_y='token_y=Dt5tbS1dEDMSYfym3fgMv0B99szno-dFc1rYF9t0aac',
+        auto_flush_rows='off',
+        auto_flush_interval='off',
+        auto_flush_bytes=64512)
+    with sender:
+        sender.row(
+            'test_table',
+            symbols={'sym': 'AAPL'},
+            columns={'price': 100.0},
+            at=ServerTimestamp)  
+
+**Equivalent questdb 2.x code with configuration string**
+
+.. code-block:: python
+
+    from questdb.ingress import Sender
+
+    conf = (
+        'tcp::addr=localhost:9009;' +
+        'username=testUser1;' +
+        'token=5UjEMuA0Pj5pjK8a-fa24dyIf-Es5mYny3oE_Wmus48;' +
+        'token_x=token_x=fLKYEaoEb9lrn3nkwLDA-M_xnuFOdSt9y0Z7_vWSHLU;' +
+        'token_y=token_y=Dt5tbS1dEDMSYfym3fgMv0B99szno-dFc1rYF9t0aac;' +
+        'auto_flush_rows=off;' +
+        'auto_flush_interval=off;' +
+        'auto_flush_bytes=64512;')
+    with Sender.from_conf(conf) as sender:
+        sender.row(
+            'test_table',
+            symbols={'sym': 'AAPL'},
+            columns={'price': 100.0},
+            at=ServerTimestamp)
+
+
+1.2.0 (2023-11-23)
+------------------
+
+This is a minor release bringing in minor new features and a few bug fixes,
+without any breaking changes.
+
+Most changes are inherited by internally upgrading to version ``3.1.0`` of
+the ``c-questdb-client``.
+
+Features
+~~~~~~~~
+
+* ``Sender(..., tls=True)`` now also uses the OS-provided certificate store.
+  The `tls` argument can now also be set to ``tls='os_roots'`` (to *only* use
+  the OS-provided certs) or ``tls='webpki_roots'`` (to *only* use the certs
+  provided by the ``webpki-roots``, i.e. the old behaviour prior to this
+  release). The new default behaviour for ``tls=True`` is equivalent to setting
+  ``tls='webpki_and_os_roots'``.
+
+* Upgraded dependencies to newer library versions. This also includes the latest
+  `webpki-roots <https://github.com/rustls/webpki-roots>`_ crate providing
+  updated TLS CA certificate roots.
+
+* Various example code and documentation improvements.
+
+Bug fixes
+~~~~~~~~~
+
+* Fixed a bug where timestamp columns could not accept values before Jan 1st
+  1970 UTC.
+
+* TCP connections now enable ``SO_KEEPALIVE``: This should ensure that
+  connections don't drop after a period of inactivity.
+
+1.1.0 (2023-01-04)
+------------------
+
+Features
+~~~~~~~~
+
+* High-performance ingestion of `Pandas <https://pandas.pydata.org/>`_
+  dataframes into QuestDB via ILP.
+  We now support most Pandas column types. The logic is implemented in native
+  code and is orders of magnitude faster than iterating the dataframe
+  in Python and calling the ``Buffer.row()`` or ``Sender.row()`` methods: The
+  ``Buffer`` can be written from Pandas at hundreds of MiB/s per CPU core.
+  The new ``dataframe()`` method continues working with the ``auto_flush``
+  feature.
+  See API documentation and examples for the new ``dataframe()`` method
+  available on both the ``Sender`` and ``Buffer`` classes.
+
+* New ``TimestampNanos.now()`` and ``TimestampMicros.now()`` methods.
+  *These are the new recommended way of getting the current timestamp.*
+
+* The Python GIL is now released during calls to ``Sender.flush()`` and when
+  ``auto_flush`` is triggered. This should improve throughput when using the
+  ``Sender`` from multiple threads.
+
+Errata
+~~~~~~
+
+* In previous releases the documentation for the ``from_datetime()`` methods of
+  the ``TimestampNanos`` and ``TimestampMicros`` types recommended calling
+  ``datetime.datetime.utcnow()`` to get the current timestamp. This is incorrect
+  as it will (confusinly) return object with the local timezone instead of UTC.
+  This documentation has been corrected and now recommends calling
+  ``datetime.datetime.now(tz=datetime.timezone.utc)`` or (more efficiently) the
+  new ``TimestampNanos.now()`` and ``TimestampMicros.now()`` methods.
+
+1.0.2 (2022-10-31)
+------------------
+
+Features
+~~~~~~~~
+
+* Support for Python 3.11.
+* Updated to version 2.1.1 of the ``c-questdb-client`` library:
+
+  * Setting ``SO_REUSEADDR`` on outbound socket. This is helpful to users with large number of connections who previously ran out of outbound network ports.
+
+
+1.0.1 (2022-08-16)
+------------------
+
+Features
+~~~~~~~~
+
+* As a matter of convenience, the ``Buffer.row`` method can now take ``None`` column
+  values. This has the same semantics as skipping the column altogether.
+  Closes `#3 <https://github.com/questdb/py-questdb-client/issues/3>`_.
+
+Bug fixes
+~~~~~~~~~
+
+* Fixed a major bug where Python ``int`` and ``float`` types were handled with
+  32-bit instead of 64-bit precision. This caused certain ``int`` values to be
+  rejected and other ``float`` values to be rounded incorrectly.
+  Closes `#13 <https://github.com/questdb/py-questdb-client/issues/13>`_.
+* Fixed a minor bug where an error auto-flush caused a second clean-up error.
+  Closes `#4 <https://github.com/questdb/py-questdb-client/issues/4>`_.
+
+
+1.0.0 (2022-07-15)
+------------------
+
+Features
+~~~~~~~~
+
+* First stable release.
+* Insert data into QuestDB via ILP.
+* Sender and Buffer APIs.
+* Authentication and TLS support.
+* Auto-flushing of buffers.
+
+
+0.0.3 (2022-07-14)
+------------------
+
+Features
+~~~~~~~~
+
+* Initial set of features to connect to the database.
+* ``Buffer`` and ``Sender`` classes.
+* First release where ``pip install questdb`` should work.
+
+
+0.0.1 (2022-07-08)
+------------------
+
+Features
+~~~~~~~~
+
+* First release on PyPI.

{questdb-1.2.0/src/questdb.egg-info → questdb-2.0.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: questdb
-Version: 1.2.0
+Version: 2.0.1
 Summary: QuestDB client library for Python
 Author-email: Adam Cimarosti <adam@questdb.io>
 License: Apache License 2.0
@@ -25,48 +25,46 @@ Classifier: Topic :: Database :: Front-Ends
 Classifier: Topic :: Scientific/Engineering
 Requires-Python: >=3.8
 Description-Content-Type: text/x-rst
+License-File: LICENSE.txt
 Provides-Extra: publish
+Requires-Dist: twine; extra == "publish"
+Requires-Dist: wheel; extra == "publish"
 Provides-Extra: ci
-License-File: LICENSE.txt
+Requires-Dist: cibuildwheel; extra == "ci"
+Provides-Extra: dataframe
+Requires-Dist: pandas; extra == "dataframe"
+Requires-Dist: pyarrow; extra == "dataframe"
+Requires-Dist: numpy; extra == "dataframe"
 
 =================================
 QuestDB Client Library for Python
 =================================
 
-This library makes it easy to insert data into `QuestDB <https://questdb.io>`_.
+This is the official Python client library for `QuestDB <https://questdb.io>`_.
 
 This client library implements QuestDB's variant of the
 `InfluxDB Line Protocol <https://questdb.io/docs/reference/api/ilp/overview/>`_
-(ILP) over TCP.
+(ILP) over HTTP and TCP.
 
 ILP provides the fastest way to insert data into QuestDB.
 
 This implementation supports `authentication
-<https://questdb.io/docs/reference/api/ilp/authenticate/>`_ and full-connection
-encryption with TLS.
+<https://py-questdb-client.readthedocs.io/en/latest/conf.html#authentication>`_
+and full-connection encryption with
+`TLS <https://py-questdb-client.readthedocs.io/en/latest/conf.html#tls>`_.
 
 Quickstart
 ==========
 
-The latest version of the library is 1.2.0.
+The latest version of the library is 2.0.1 (`changelog <https://py-questdb-client.readthedocs.io/en/latest/changelog.html>`_).
 
 ::
 
-    python3 -m pip install questdb
-
-.. code-block:: python
+    python3 -m pip install -U questdb[dataframe]
 
-    from questdb.ingress import Sender, TimestampNanos
-
-    with Sender('localhost', 9009) as sender:
-        sender.row(
-            'sensors',
-            symbols={'id': 'toronto1'},
-            columns={'temperature': 20.0, 'humidity': 0.5},
-            at=TimestampNanos.now())
-        sender.flush()
+Please start by `setting up QuestDB <https://questdb.io/docs/quick-start/>`_ . Once set up, you can use this library to insert data.
 
-You can also send Pandas dataframes:
+The most common way to insert data is from a Pandas dataframe.
 
 .. code-block:: python
 
@@ -79,33 +77,61 @@ You can also send Pandas dataframes:
         'humidity': [0.5, 0.6],
         'timestamp': pd.to_datetime(['2021-01-01', '2021-01-02'])})
 
-    with Sender('localhost', 9009) as sender:
+    conf = f'http::addr=localhost:9000;'
+    with Sender.from_conf(conf) as sender:
         sender.dataframe(df, table_name='sensors', at='timestamp')
 
+You can also send individual rows. This only requires a more minimal installation::
+
+    python3 -m pip install -U questdb
+
+.. code-block:: python
+
+    from questdb.ingress import Sender, TimestampNanos
+
+    conf = f'http::addr=localhost:9000;'
+    with Sender.from_conf(conf) as sender:
+        sender.row(
+            'sensors',
+            symbols={'id': 'toronto1'},
+            columns={'temperature': 20.0, 'humidity': 0.5},
+            at=TimestampNanos.now())
+        sender.flush()
 
-Docs
-====
 
-https://py-questdb-client.readthedocs.io/
+To connect via the `older TCP protocol <https://py-questdb-client.readthedocs.io/en/latest/sender.html#ilp-tcp-or-ilp-http>`_, set the
+`configuration string <https://py-questdb-client.readthedocs.io/en/latest/conf.html>`_ to:
 
+.. code-block:: python
 
-Code
-====
+    conf = f'tcp::addr=localhost:9009;'
+    with Sender.from_conf(conf) as sender:
+        ...
 
-https://github.com/questdb/py-questdb-client
 
+You can continue by reading the
+`Sending Data Over ILP <https://py-questdb-client.readthedocs.io/en/latest/sender.html>`_
+guide.
 
-Package on PyPI
-===============
+Links
+=====
 
-https://pypi.org/project/questdb/
+* `Core database documentation <https://questdb.io/docs/>`_
 
+* `Python library documentation <https://py-questdb-client.readthedocs.io/>`_
+
+* `GitHub repository <https://github.com/questdb/py-questdb-client>`_
+
+* `Package on PyPI <https://pypi.org/project/questdb/>`_
 
 Community
 =========
 
-If you need help, have additional questions or want to provide feedback, you
-may find us on `Slack <https://slack.questdb.io>`_.
+If you need help, you can ask on `Stack Overflow
+<https://stackoverflow.com/questions/ask?tags=questdb&tags=py-questdb-client>`_:
+We monitor the ``#questdb`` and ``#py-questdb-client`` tags.
+
+Alternatively, you may find us on `Slack <https://slack.questdb.io>`_.
 
 You can also `sign up to our mailing list <https://questdb.io/community/>`_
 to get notified of new releases.

questdb-2.0.1/README.rst

@@ -0,0 +1,106 @@
+=================================
+QuestDB Client Library for Python
+=================================
+
+This is the official Python client library for `QuestDB <https://questdb.io>`_.
+
+This client library implements QuestDB's variant of the
+`InfluxDB Line Protocol <https://questdb.io/docs/reference/api/ilp/overview/>`_
+(ILP) over HTTP and TCP.
+
+ILP provides the fastest way to insert data into QuestDB.
+
+This implementation supports `authentication
+<https://py-questdb-client.readthedocs.io/en/latest/conf.html#authentication>`_
+and full-connection encryption with
+`TLS <https://py-questdb-client.readthedocs.io/en/latest/conf.html#tls>`_.
+
+Quickstart
+==========
+
+The latest version of the library is 2.0.1 (`changelog <https://py-questdb-client.readthedocs.io/en/latest/changelog.html>`_).
+
+::
+
+    python3 -m pip install -U questdb[dataframe]
+
+Please start by `setting up QuestDB <https://questdb.io/docs/quick-start/>`_ . Once set up, you can use this library to insert data.
+
+The most common way to insert data is from a Pandas dataframe.
+
+.. code-block:: python
+
+    import pandas as pd
+    from questdb.ingress import Sender
+
+    df = pd.DataFrame({
+        'id': pd.Categorical(['toronto1', 'paris3']),
+        'temperature': [20.0, 21.0],
+        'humidity': [0.5, 0.6],
+        'timestamp': pd.to_datetime(['2021-01-01', '2021-01-02'])})
+
+    conf = f'http::addr=localhost:9000;'
+    with Sender.from_conf(conf) as sender:
+        sender.dataframe(df, table_name='sensors', at='timestamp')
+
+You can also send individual rows. This only requires a more minimal installation::
+
+    python3 -m pip install -U questdb
+
+.. code-block:: python
+
+    from questdb.ingress import Sender, TimestampNanos
+
+    conf = f'http::addr=localhost:9000;'
+    with Sender.from_conf(conf) as sender:
+        sender.row(
+            'sensors',
+            symbols={'id': 'toronto1'},
+            columns={'temperature': 20.0, 'humidity': 0.5},
+            at=TimestampNanos.now())
+        sender.flush()
+
+
+To connect via the `older TCP protocol <https://py-questdb-client.readthedocs.io/en/latest/sender.html#ilp-tcp-or-ilp-http>`_, set the
+`configuration string <https://py-questdb-client.readthedocs.io/en/latest/conf.html>`_ to:
+
+.. code-block:: python
+
+    conf = f'tcp::addr=localhost:9009;'
+    with Sender.from_conf(conf) as sender:
+        ...
+
+
+You can continue by reading the
+`Sending Data Over ILP <https://py-questdb-client.readthedocs.io/en/latest/sender.html>`_
+guide.
+
+Links
+=====
+
+* `Core database documentation <https://questdb.io/docs/>`_
+
+* `Python library documentation <https://py-questdb-client.readthedocs.io/>`_
+
+* `GitHub repository <https://github.com/questdb/py-questdb-client>`_
+
+* `Package on PyPI <https://pypi.org/project/questdb/>`_
+
+Community
+=========
+
+If you need help, you can ask on `Stack Overflow
+<https://stackoverflow.com/questions/ask?tags=questdb&tags=py-questdb-client>`_:
+We monitor the ``#questdb`` and ``#py-questdb-client`` tags.
+
+Alternatively, you may find us on `Slack <https://slack.questdb.io>`_.
+
+You can also `sign up to our mailing list <https://questdb.io/community/>`_
+to get notified of new releases.
+
+
+License
+=======
+
+The code is released under the `Apache License 2.0
+<https://github.com/questdb/py-questdb-client/blob/main/LICENSE.txt>`_.

{questdb-1.2.0 → questdb-2.0.1}/c-questdb-client/.bumpversion.cfg

@@ -1,5 +1,5 @@
 [bumpversion]
-current_version = 3.1.0
+current_version = 4.0.0
 commit = True
 tag = False
 
@@ -26,3 +26,7 @@ replace = questdb-rs/{new_version}/
 [bumpversion:file:questdb-rs-ffi/Cargo.toml]
 search = version = "{current_version}"
 replace = version = "{new_version}"
+
+[bumpversion:file:include/questdb/ingress/line_sender.hpp]
+search = questdb/c++/{current_version}
+replace = questdb/c++/{new_version}

{questdb-1.2.0 → questdb-2.0.1}/c-questdb-client/CMakeLists.txt

@@ -1,5 +1,5 @@
 cmake_minimum_required(VERSION 3.15.0)
-project(c-questdb-client VERSION 3.1.0)
+project(c-questdb-client VERSION 4.0.0)
 
 set(CPACK_PROJECT_NAME ${PROJECT_NAME})
 set(CPACK_PROJECT_VERSION ${PROJECT_VERSION})
@@ -90,16 +90,30 @@ endfunction()
 if (QUESTDB_TESTS_AND_EXAMPLES)
     compile_example(
         line_sender_c_example
+        examples/concat.c
         examples/line_sender_c_example.c)
     compile_example(
         line_sender_c_example_auth
+        examples/concat.c
         examples/line_sender_c_example_auth.c)
     compile_example(
         line_sender_c_example_tls_ca
+        examples/concat.c
         examples/line_sender_c_example_tls_ca.c)
     compile_example(
         line_sender_c_example_auth_tls
+        examples/concat.c
         examples/line_sender_c_example_auth_tls.c)
+    compile_example(
+        line_sender_c_example_http
+        examples/concat.c
+        examples/line_sender_c_example_http.c)
+    compile_example(
+        line_sender_c_example_from_conf
+        examples/line_sender_c_example_from_conf.c)
+    compile_example(
+        line_sender_c_example_from_env
+        examples/line_sender_c_example_from_env.c)
     compile_example(
         line_sender_cpp_example
         examples/line_sender_cpp_example.cpp)
@@ -112,6 +126,15 @@ if (QUESTDB_TESTS_AND_EXAMPLES)
     compile_example(
         line_sender_cpp_example_auth_tls
         examples/line_sender_cpp_example_auth_tls.cpp)
+    compile_example(
+        line_sender_cpp_example_http
+        examples/line_sender_cpp_example_http.cpp)
+    compile_example(
+        line_sender_cpp_example_from_conf
+        examples/line_sender_cpp_example_from_conf.cpp)
+    compile_example(
+        line_sender_cpp_example_from_env
+        examples/line_sender_cpp_example_from_env.cpp)
 
     # Include Rust tests as part of the tests run
     add_test(

{questdb-1.2.0 → questdb-2.0.1}/c-questdb-client/README.md

@@ -4,7 +4,7 @@
 This library makes it easy to insert data into [QuestDB](https://questdb.io/).
 
 This client library implements the [InfluxDB Line Protocol](
-https://questdb.io/docs/reference/api/ilp/overview/) (ILP) over TCP.
+https://questdb.io/docs/reference/api/ilp/overview/) (ILP) over TCP or HTTP.
 
 * Implementation is in Rust, with no additional
   [run-time or link-time dependencies](doc/BUILD.md#pre-requisites-and-dependencies)
@@ -16,21 +16,21 @@ https://questdb.io/docs/reference/api/ilp/overview/) (ILP) over TCP.
 
 ## Insertion Protocols Overview
 
-Inserting data into QuestDB can be done via one of three protocols.
+Inserting data into QuestDB can be done in several ways.
+
+This library supports ILP/HTTP (default-recommended) and ILP/TCP (specific
+streaming use cases).
 
 | Protocol | Record Insertion Reporting | Data Insertion Performance |
 | -------- | -------------------------- | -------------------------- |
-| [ILP](https://questdb.io/docs/reference/api/ilp/overview/)| Errors in logs; Disconnect on error | **Best** |
+| **[ILP/HTTP](https://questdb.io/docs/reference/api/ilp/overview/)** | Transaction-level (on flush) | **Excellent** |
+| [ILP/TCP](https://questdb.io/docs/reference/api/ilp/overview/)| Errors in logs; Disconnect on error | **Best** (tolerates higher latency networks) |
 | [CSV Upload via HTTP](https://questdb.io/docs/reference/api/rest/#imp---import-data) | Configurable | Very Good |
 | [PostgreSQL](https://questdb.io/docs/reference/api/postgres/) | Transaction-level | Good |
 
-This library implements the **ILP protocol** and mitigates the lack of confirmation
-and error reporting by validating data ahead of time before any data is sent
-to the database instance.
-
-For example, the client library will report that a supplied string isn't encoded
-in UTF-8. Some issues unfortunately can't be caught by the library and require
-some [care and diligence to avoid data problems](doc/CONSIDERATIONS.md).
+Server errors are only reported back to the client for ILP/HTTP.
+See the [flush troubleshooting](doc/CONSIDERATIONS.md) docs for more details on
+how to debug ILP/TCP.
 
 For an overview and code examples, see the
 [ILP page of the developer docs](https://questdb.io/docs/develop/insert-data/#influxdb-line-protocol).