blob: af1c134077b02c4df98e8ec1c79ffd2fe1268151 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
|
#pragma once
#include <Storages/IStorage.h>
namespace DB
{
/* One block storage used for values table function
* It's structure is similar to IStorageSystemOneBlock
*/
class StorageValues final : public IStorage
{
public:
StorageValues(
const StorageID & table_id_, const ColumnsDescription & columns_, const Block & res_block_, const NamesAndTypesList & virtuals_ = {});
std::string getName() const override { return "Values"; }
Pipe read(
const Names & column_names,
const StorageSnapshotPtr & storage_snapshot,
SelectQueryInfo & query_info,
ContextPtr context,
QueryProcessingStage::Enum processed_stage,
size_t max_block_size,
size_t num_streams) override;
/// Why we may have virtual columns in the storage from a single block?
/// Because it used as tmp storage for pushing blocks into views, and some
/// views may contain virtual columns from original storage.
NamesAndTypesList getVirtuals() const override
{
return virtuals;
}
/// FIXME probably it should return false, but StorageValues is used in ExecutingInnerQueryFromViewTransform (whatever it is)
bool supportsTransactions() const override { return true; }
bool parallelizeOutputAfterReading(ContextPtr) const override { return false; }
private:
Block res_block;
NamesAndTypesList virtuals;
};
}
|
