- Learning Apache Cassandra(Second Edition)
- Sandeep Yarabarla
- 244字
- 2021-07-03 00:19:31
Selecting data
We now know how to retrieve data from the database, but that isn't much good unless we can get it back again. Let's say we now want to build an account settings page for MyStatus; we've got the user's username stored in a persistent session, but we will retrieve the other profile fields from the database to display in the settings form:
SELECT * FROM "users"
WHERE "username" = 'alice';
This query tells Cassandra we want to retrieve the rows where the value for username (the primary key) is alice. The * wildcard simply says we would like all the columns in that row, saving us from having to type them all out. You'll see the rows we requested nicely formatted in the CQL shell as follows:
In other scenarios, we don't need all the columns. When a user tries to log in to MyStatus, we want to retrieve their password and compare it to the one the user provided us with, but we don't care about the email. Avoiding unnecessary columns reduces the amount of data that needs to be transferred between Cassandra and our application, thus making the queries faster. Instead of using the (*) wildcard, we can instead type a list of columns we are interested in:
SELECT "username", "encrypted_password" FROM "users"
WHERE "username" = 'alice';
You'll see that in the results, the email column no longer appears since it wasn't in the list of columns that we specified.
- CompTIA Linux+ Certification Guide
- 自動控制理論(非自動化專業)
- 項目管理成功利器Project 2007全程解析
- 電氣控制與PLC技術應用
- 數字多媒體技術基礎
- 深度學習原理與 TensorFlow實踐
- 30天學通Java Web項目案例開發
- 企業級Web開發實戰
- 機器人剛柔耦合動力學
- PostgreSQL High Performance Cookbook
- 基于元胞自動機的人群疏散系統建模與分析
- 玩轉機器人:基于Proteus的電路原理仿真(移動視頻版)
- Spark Streaming實時流式大數據處理實戰
- Python Data Mining Quick Start Guide
- ORACLE數據庫技術實用詳解