Re: [DISCUSSION] Key and Value fields with same name and SQL DML

2020-06-15 Thread Alexey Sasov
Denis, hello. Thanks for your explanation. I can see some difficulties in matching your new idea with the current functionality of key-value approach. >From this point of view, Alexey Kukushkin's approach looks less confusing to me and easier to implement. But this could be due to the lack of under

Re: [DISCUSSION] Key and Value fields with same name and SQL DML

2020-05-26 Thread Alexey Sasov
Hello. Looks good. What whould be returned from the query like this "select _key from cache" if we don't know the type of the key? ExpandoObject, Tuple, BinaryObject? How would you change ICache interface which has this member? /// Queries cache. /// Query. /// Cursor. IQueryCursor

Re: [DISCUSSION] Key and Value fields with same name and SQL DML

2020-05-21 Thread Alexey Sasov
Hello, Denis. This is the analogy of DB records. We've got keys in the table. But querying the record with the key we also have this key in the returned record. The question of having all data in the value is a domain driven one. If i have a model (ex. Person) containing PassportNo, I don't want to

Re: [DISCUSSION] Key and Value fields with same name and SQL DML

2020-05-20 Thread Alexey Sasov
Hello. Sure this feature is of great importance and we'd like to get it asap. It is very confusing to support the logic of copying values between key and value classes. Thanks. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/