From dddca2d3b57470cf210824543973e68d0cfa4258 Mon Sep 17 00:00:00 2001 From: M1ha Date: Wed, 8 Feb 2017 11:05:13 +0500 Subject: [PATCH] Corrected links and code --- README.rst | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/README.rst b/README.rst index d68e04f..4a3c7b8 100644 --- a/README.rst +++ b/README.rst @@ -186,15 +186,15 @@ inconsistencies in the pagination (such as an instance that appears on two diffe System models ------------- -`Clickhouse docs ` +`Clickhouse docs `_. System models are read only models for implementing part of the system's functionality, and for providing access to information about how the system is working. -Usage example: +Usage example:: >>>> from infi.clickhouse_orm import system_models - >>>> print(system_models.SystemPart.all()) + >>>> print(system_models.SystemPart.get(Database())) Currently the following system models are supported: @@ -208,7 +208,7 @@ SystemPart system.parts Gives methods to work with partitions. See Partitions and parts -------------------- -`ClickHouse docs ` +`ClickHouse docs `_. A partition in a table is data for a single calendar month. Table "system.parts" contains information about each part. @@ -324,7 +324,8 @@ You can create array fields containing any data type, for example:: Working with materialized and alias fields ****************************************** -ClickHouse provides an opportunity to create MATERIALIZED and ALIAS fields. +ClickHouse provides an opportunity to create MATERIALIZED and ALIAS Fields. + See documentation `here `_. Both field types can't be inserted into the database directly, so they are ignored when using the ``Database.insert()`` method.