Skip to content

Provide a request / a statement object in noSQL API #212

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
Totktonada opened this issue Aug 2, 2019 · 2 comments
Open

Provide a request / a statement object in noSQL API #212

Totktonada opened this issue Aug 2, 2019 · 2 comments
Labels
enhancement raw idea

Comments

@Totktonada
Copy link
Member

The alternative Java connector has ability to, say, construct update statement step-by-step. This can be more intuitive then our way.

Don't sure whether it worth to do so, looks as the minor improvement.
@Totktonada Totktonada mentioned this issue Aug 2, 2019
Merged
nicktorwald added a commit that referenced this issue Sep 4, 2019
@nicktorwald
Soft automatic schema reload
8ef4616 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

This also includes set of request builders that can be used as a public
API to construct requests. The main idea here is to provide more
natural DSL-like approach to build operations instead of current
abstract types like List<?> or List<Object>.

Closes: #7, #137
Affects: #212
nicktorwald added a commit that referenced this issue Sep 4, 2019
@nicktorwald
Soft automatic schema reload
e99d0dd 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

This also includes set of request builders that can be used as a public
API to construct requests. The main idea here is to provide more
natural DSL-like approach to build operations instead of current
abstract types like List<?> or List<Object>.

Closes: #7, #137
Affects: #212
@rybakit
Copy link

rybakit commented Sep 5, 2019

For the record, the alternative PHP connector has this feature as well. It has the Operations class for update requests and Criteria for selects. Here are a few examples:

$result1 = $space->select(Criteria::key([1]));
$result2 = $space->select(Criteria::index('secondary')
    ->andKey(['bar'])
    ->andLimit(2)
    ->andOffset(1)
);
$result = $space->update([2], Operations::add(1, 5)->andSet(2, 'BAR'));

nicktorwald added a commit that referenced this issue Sep 5, 2019
@nicktorwald
Soft automatic schema reload
fd33520 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

This also includes set of request builders that can be used as a public
API to construct requests. The main idea here is to provide more
natural DSL-like approach to build operations instead of current
abstract types like List<?> or List<Object>.

Closes: #7, #137
Affects: #212
nicktorwald added a commit that referenced this issue Sep 6, 2019
@nicktorwald
Soft automatic schema reload
39b7dfb 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

This also includes set of request builders that can be used as a public
API to construct requests. The main idea here is to provide more
natural DSL-like approach to build operations instead of current
abstract types like List<?> or List<Object>.

Closes: #7, #137
Affects: #212
nicktorwald added a commit that referenced this issue Sep 6, 2019
@nicktorwald
Soft automatic schema reload
7f107c0 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

This also includes set of request builders that can be used as a public
API to construct requests. The main idea here is to provide more
natural DSL-like approach to build operations instead of current
abstract types like List<?> or List<Object>.

Closes: #7, #137
Affects: #212
nicktorwald added a commit that referenced this issue Sep 8, 2019
@nicktorwald
Soft automatic schema reload
05d7b8c 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

This also includes set of request builders that can be used as a public
API to construct requests. The main idea here is to provide more
natural DSL-like approach to build operations instead of current
abstract types like List<?> or List<Object>.

Closes: #7, #137
Affects: #212
nicktorwald added a commit that referenced this issue Sep 8, 2019
@nicktorwald
Soft automatic schema reload
6ffa1a5 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

This also includes set of request builders that can be used as a public
API to construct requests. The main idea here is to provide more
natural DSL-like approach to build operations instead of current
abstract types like List<?> or List<Object>.

Closes: #7, #137
Affects: #212
nicktorwald added a commit that referenced this issue Sep 8, 2019
@nicktorwald
Soft automatic schema reload
8aed0a1 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

This also includes set of request builders that can be used as a public
API to construct requests. The main idea here is to provide more
natural DSL-like approach to build operations instead of current
abstract types like List<?> or List<Object>.

Closes: #7, #137
Affects: #212
nicktorwald added a commit that referenced this issue Sep 8, 2019
@nicktorwald
Soft automatic schema reload
456385e 
Now client keeps actual schema metadata and sends schemaId header to be
checked against current Tarantool schema version. If client version
mismatches DB version client does schema reloading in the background.

Client operation interface was reworked in scope of support not only
number identifiers for spaces and indexes but also their string names.

This also includes set of request builders that can be used as a public
API to construct requests. The main idea here is to provide more
natural DSL-like approach to build operations instead of current
abstract types like List<?> or List<Object>.

Closes: #7, #137
Affects: #212
nicktorwald added a commit that referenced this issue Sep 18, 2019
@nicktorwald
Introduce Tarantool client DSL
62c8912 
This DSL includes set of request builders that can be used as a public
API to construct requests. The main idea here is to provide more
natural DSL-like approach to build operations instead of current
abstract types like List<?> or List<Object>.

Affects: #212
nicktorwald added a commit that referenced this issue Sep 18, 2019
@nicktorwald
Introduce Tarantool client DSL
5ffc288 
This DSL includes set of request builders that can be used as a public
API to construct requests. The main idea here is to provide more
natural DSL-like approach to build operations instead of current
abstract types like List<?> or List<Object>.

Affects: #212
nicktorwald added a commit that referenced this issue Sep 19, 2019
@nicktorwald
Introduce Tarantool client DSL
244a493 
This DSL includes set of request builders that can be used as a public
API to construct requests. The main idea here is to provide more
natural DSL-like approach to build operations instead of current
abstract types like List<?> or List<Object>.

Affects: #212
nicktorwald added a commit that referenced this issue Oct 25, 2019
@nicktorwald
Introduce Tarantool client DSL
d5ceeb2 
This DSL includes set of request builders that can be used as a public
API to construct requests. The main idea here is to provide more
natural DSL-like approach to build operations instead of current
abstract types like List<?> or List<Object>.

Affects: #212
nicktorwald added a commit that referenced this issue Nov 20, 2019
@nicktorwald
Introduce Tarantool client DSL
9cedcd2 
This DSL includes set of request builders that can be used as a public
API to construct requests. The main idea here is to provide more
natural DSL-like approach to build operations instead of current
abstract types like List<?> or List<Object>.

Affects: #212
nicktorwald added a commit that referenced this issue Nov 20, 2019
@nicktorwald
Introduce Tarantool client DSL
c06f6a9 
This DSL includes set of request builders that can be used as a public
API to construct requests. The main idea here is to provide more
natural DSL-like approach to build operations instead of current
abstract types like List<?> or List<Object>.

Closes: #212
@nicktorwald nicktorwald mentioned this issue Nov 20, 2019
Closed
nicktorwald added a commit that referenced this issue Nov 20, 2019
@nicktorwald
Introduce Tarantool client DSL
63f1dee 
This DSL includes set of request builders that can be used as a public
API to construct requests. The main idea here is to provide more
natural DSL-like approach to build operations instead of current
abstract types like List<?> or List<Object>.

Closes: #212
@Totktonada
Copy link
Member Author

I propose to provide only new upsert operation in this API, see #248.

nicktorwald added a commit that referenced this issue Nov 26, 2019
@nicktorwald
dsl: introduce Tarantool client DSL
45e4b39 
This DSL includes set of request builders that can be used as a public
API to construct requests. The main idea here is to provide more
natural DSL-like approach to build operations instead of current
abstract types like List<?> or List<Object>.

Closes: #212
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement raw idea
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Introduce Tarantool client DSL tarantool/tarantool-java
2 participants
@Totktonada @rybakit