document/current/en/features/encrypt/index.xml (36 lines of code) (raw):

<?xml version="1.0" encoding="utf-8" standalone="yes"?> <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> <channel> <title>Encryption on ShardingSphere</title> <link>https://shardingsphere.apache.org/document/current/en/features/encrypt/</link> <description>Recent content in Encryption on ShardingSphere</description> <generator>Hugo -- gohugo.io</generator> <language>en-us</language> <atom:link href="https://shardingsphere.apache.org/document/current/en/features/encrypt/index.xml" rel="self" type="application/rss+xml" /> <item> <title>Core Concept</title> <link>https://shardingsphere.apache.org/document/current/en/features/encrypt/concept/</link> <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> <guid>https://shardingsphere.apache.org/document/current/en/features/encrypt/concept/</guid> <description>Logic column It is used to calculate the encryption and decryption columns and it is the logical identifier of the column in SQL. Logical columns contain ciphertext columns (mandatory), query-helper columns (optional), like-query columns (optional), and plaintext columns (optional). Cipher column Encrypted data columns. Assisted query column It is a helper column used for queries. For some non-idempotent encryption algorithms with higher security levels, irreversible idempotent columns are provided for queries.</description> </item> <item> <title>Limitations</title> <link>https://shardingsphere.apache.org/document/current/en/features/encrypt/limitations/</link> <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> <guid>https://shardingsphere.apache.org/document/current/en/features/encrypt/limitations/</guid> <description>You need to process the original data on stocks in the database by yourself. The like query supports %, _, but currently does not support escape. Case insensitive queries are not supported for the encrypted fields. Comparison operations are not supported for encrypted fields, such as GREATER THAN, LESS THAN, ORDER BY, BETWEEN. Calculation operations are not supported for encrypted fields, such as AVG, SUM, and computation expressions. When projection subquery contains encrypt column, you must use alias.</description> </item> <item> <title>Appendix with SQL operator</title> <link>https://shardingsphere.apache.org/document/current/en/features/encrypt/appendix/</link> <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> <guid>https://shardingsphere.apache.org/document/current/en/features/encrypt/appendix/</guid> <description>Unsupported SQL: The case-insensitive queries are not supported by encrypted fields. Comparison operations are not supported for encrypted fields, such as GREATER THAN, LESS THAN, ORDER BY, BETWEEN. Calculation operations are not supported for encrypted fields, such as AVG, SUM, and computation expressions. SQL that contains encrypt column in subquery and uses asterisks for outer projection is not supported. Other: You should keep encrypt columns, assisted columns and like columns in encrypt rule same capitalization with columns in database.</description> </item> </channel> </rss>