summaryrefslogtreecommitdiff
path: root/src/t_string.c
Commit message (Collapse)AuthorAgeFilesLines
* More obvious indentation in setCommand().antirez2015-02-031-4/+8
|
* Merge branch 'unstable' of git://github.com/mihirvj/redis into set-prantirez2015-02-031-4/+12
|\
| * Stricter options for SET commandMihir Joshi2014-12-141-8/+12
| | | | | | | | | | - As per Antirez's suggestion, this commit raises an error when mutually exclusive options are provided. Duplicate options are allowed.
| * stricter options for SET commandMihir Joshi2014-11-211-4/+8
| | | | | | | | | | | | | | | | | | | | | | Issue: #2157 As the SET command is parsed, it remembers which options are already set and if a duplicate option is found, raises an error because it is essentially an invalid syntax. It still allows mutually exclusive options like EX and PX because taking an option over another (precedence) is not essentially a syntactic error.
* | Use exp format and more precision output for ZSCAN.antirez2014-12-021-1/+1
|/ | | | Ref: issue #2175
* INCR: Modify incremented object in-place when possible.antirez2014-10-031-5/+15
| | | | | | | | | However we don't try to do this if the integer is already inside a range representable with a shared integer. The performance gain appears to be around ~15% in micro benchmarks, however in the long run this also helps to improve locality, so should have more, hard to measure, benefits.
* Return empty string if GETRANGE of empty stringMatt Stancliff2014-09-021-1/+1
| | | | | | | Previously, GETRANGE of a key containing nothing ("") would allocate a large (size_t)-1 return value causing crashes on 32bit builds when it tried to allocate the 4 GB return string.
* Increase size of range request in getrangeMatt Stancliff2014-09-021-4/+4
| | | | | | | | | | 32 bit builds don't have a big enough long to capture the same range as a 64 bit build. If we use "long long" we get proper size limits everywhere. Also updates size of unsigned comparison to fit new size of `end`. Fixes #1981
* Fix invalid expire error for SET family commands.antirez2014-08-181-1/+1
|
* Handle large getrange requestsJan-Erik Rediger2014-08-071-1/+1
| | | | | | | | Previously the end was casted to a smaller type which resulted in a wrong check and failed with values larger than handled by unsigned. Closes #1847, #1844
* String value unsharing refactored into proper function.antirez2014-03-301-14/+2
| | | | | | | | | | | All the Redis functions that need to modify the string value of a key in a destructive way (APPEND, SETBIT, SETRANGE, ...) require to make the object unshared (if refcount > 1) and encoded in raw format (if encoding is not already REDIS_ENCODING_RAW). This was cut & pasted many times in multiple places of the code. This commit puts the small logic needed into a function called dbUnshareStringValue().
* Introduction of a new string encoding: EMBSTRantirez2013-07-221-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously two string encodings were used for string objects: 1) REDIS_ENCODING_RAW: a string object with obj->ptr pointing to an sds stirng. 2) REDIS_ENCODING_INT: a string object where the obj->ptr void pointer is casted to a long. This commit introduces a experimental new encoding called REDIS_ENCODING_EMBSTR that implements an object represented by an sds string that is not modifiable but allocated in the same memory chunk as the robj structure itself. The chunk looks like the following: +--------------+-----------+------------+--------+----+ | robj data... | robj->ptr | sds header | string | \0 | +--------------+-----+-----+------------+--------+----+ | ^ +-----------------------+ The robj->ptr points to the contiguous sds string data, so the object can be manipulated with the same functions used to manipulate plan string objects, however we need just on malloc and one free in order to allocate or release this kind of objects. Moreover it has better cache locality. This new allocation strategy should benefit both the memory usage and the performances. A performance gain between 60 and 70% was observed during micro-benchmarks, however there is more work to do to evaluate the performance impact and the memory usage behavior.
* Support for case unsensitive SET options.charsyam2013-03-291-4/+8
|
* Extended SET command implemented (issue #931).antirez2013-03-281-8/+58
|
* Keyspace events: it is now possible to select subclasses of events.antirez2013-01-281-8/+10
| | | | | | | | | When keyspace events are enabled, the overhead is not sever but noticeable, so this commit introduces the ability to select subclasses of events in order to avoid to generate events the user is not interested in. The events can be selected using redis.conf or CONFIG SET / GET.
* Keyspace events added for more commands.antirez2013-01-281-1/+3
|
* Initial test events for the new keyspace notification API.antirez2013-01-281-0/+6
|
* Additionally two typos fixed thanks to @jodalantirez2013-01-191-1/+1
|
* Fixed many typos.guiquanz2013-01-191-2/+2
|
* BSD license added to every C source and header file.antirez2012-11-081-0/+29
|
* Invert two sides of if expression in SET to avoid a lookup.antirez2012-10-311-1/+1
| | | | | | | | Because of the short circuit behavior of && inverting the two sides of the if expression avoids an hash table lookup if the non-EX variant of SET is called. Thanks to Weibin Yao (@yaoweibin on github) for spotting this.
* Bit-related string operations moved to bitop.cantirez2012-05-241-248/+0
| | | | | | | | | | | | | | | All the general string operations are implemented in t_string.c, however the bit operations, while targeting the string type, are better served in a specific file where we have the implementations of the following four commands and helper functions: GETBIT SETBIT BITOP BITCOUNT In the future this file will probably contain more code related to making the BITOP and BITCOUNT operations faster.
* New commands: BITOP and BITCOUNT.antirez2012-05-241-0/+149
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The motivation for this new commands is to be search in the usage of Redis for real time statistics. See the article "Fast real time metrics using Redis". http://blog.getspool.com/2011/11/29/fast-easy-realtime-metrics-using-redis-bitmaps/ In general Redis strings when used as bitmaps using the SETBIT/GETBIT command provide a very space-efficient and fast way to store statistics. For instance in a web application with users, every user can be associated with a key that shows every day in which the user visited the web service. This information can be really valuable to extract user behaviour information. With Redis bitmaps doing this is very simple just saying that a given day is 0 (the data the service was put online) and all the next days are 1, 2, 3, and so forth. So with SETBIT it is possible to set the bit corresponding to the current day every time the user visits the site. It is possible to take the count of the bit sets on the run, this is extremely easy using a Lua script. However a fast bit count native operation can be useful, especially if it can operate on ranges, or when the string is small like in the case of days (even if you consider many years it is still extremely little data). For this reason BITOP was introduced. The command counts the number of bits set to 1 in a string, with optional range: BITCOUNT key [start end] The start/end parameters are similar to GETRANGE. If omitted the whole string is tested. Population counting is more useful when bit-level operations like AND, OR and XOR are avaialble. For instance I can test multiple users to see the number of days three users visited the site at the same time. To do this we can take the AND of all the bitmaps, and then count the set bits. For this reason the BITOP command was introduced: BITOP [AND|OR|XOR|NOT] dest_key src_key1 src_key2 src_key3 ... src_keyN In the special case of NOT (that inverts the bits) only one source key can be passed. The judicious use of BITCOUNT and BITOP combined can lead to interesting use cases with very space efficient representation of data. The implementation provided is still not tested and optimized for speed, next commits will introduce unit tests. Later the implementation will be profiled to see if it is possible to gain an important amount of speed without making the code much more complex.
* Fixed undefined behavior in *INCR style functions overflow detection. Sorry ↵antirez2012-02-211-2/+3
| | | | clang!
* rewrite INCRBYFLOAT as SETs for AOF/replicationantirez2011-11-141-1/+9
|
* INCRBYFLOAT implementationantirez2011-11-121-0/+26
|
* high resolution expires API modified to use separated commands. AOF ↵antirez2011-11-101-8/+14
| | | | transation to PEXPIREAT of all the expire-style commands fixed.
* Initial support for key expire times with millisecond resolution. RDB ↵antirez2011-11-091-1/+1
| | | | version is now 3, new opcoded added for high resolution times. Redis is still able to correctly load RDB version 2. Tests passing but still a work in progress. API to specify milliseconds expires still missing, but the precision of normal expires is now already improved and working.
* useless call removed, thanks to Pieter for spotting thisantirez2011-06-201-1/+0
|
* DB API refactoring. The changes were designed together with Pieter Noordhuis.antirez2011-06-201-32/+20
|
* Fixed return value of GETRANGE / SUBSTRantirez2011-03-041-2/+2
|
* Merge branch 'master' into unstableantirez2011-01-041-1/+0
|\
| * limits.h is already included from redis.hPieter Noordhuis2010-12-231-1/+0
| |
* | touched key for WATCH refactored into a more general thing that can be used ↵antirez2010-12-291-7/+7
|/ | | | also for the cache system. Some more changes towards diskstore working.
* overflow detection in INCR family functionsantirez2010-12-191-1/+6
|
* Use helper function for string object lengthPieter Noordhuis2010-12-151-20/+3
|
* Use helper functions in APPENDPieter Noordhuis2010-12-151-14/+8
|
* Disable negative offsets for SETRANGEPieter Noordhuis2010-12-151-12/+5
|
* Make SETBIT return original bit valuePieter Noordhuis2010-12-151-16/+25
|
* removed a test that will never be true fixing the compilation on Linuxantirez2010-12-141-4/+2
|
* Refactor and rename SUBSTR to GETRANGEPieter Noordhuis2010-12-141-37/+37
| | | | | SUBSTR is renamed to GETRANGE to have better consistency between command names (with SETRANGE as its dual). GETRANGE is still aliased as SUBSTR.
* Add SETRANGE command implementation and testsPieter Noordhuis2010-12-141-0/+85
|
* Don't decode object on STRLEN when not necessaryPieter Noordhuis2010-12-141-3/+10
|
* Change function name to match what it doesPieter Noordhuis2010-12-101-1/+1
|
* TypoPieter Noordhuis2010-12-101-1/+1
|
* Add generic function to grow an sds valuePieter Noordhuis2010-12-101-8/+18
| | | | | | Move logic concerned with setting a bit in an sds to the SETBIT command instead of keeping it in sds.c. The function to grow an sds can and will be reused for a command to set a range within a string value.
* Enforce maximum string value length of 512MBPieter Noordhuis2010-12-091-13/+17
|
* Add commands SETBIT/GETBITPieter Noordhuis2010-12-091-0/+82
|
* Convert objects in the command procs instead of the protocol codePieter Noordhuis2010-10-171-0/+5
|
* Use specialized function to add status and error repliesPieter Noordhuis2010-09-021-2/+2
|
View Lorry Controller Status