Hawkin
/
arangodb
mirror of https://gitee.com/bigwinds/arangodb
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
8,041 Commits 358 Branches 495 Tags 994 MiB
Commit Graph

223 Commits

Author SHA1 Message Date
Jan Steemann 669957e81d fixed test after web interface change 2013-08-26 17:05:32 +02:00
Jan Steemann 38abd5bf9e issue #576 2013-08-21 14:02:09 +02:00
Jan Steemann 38d8b0b598 adjusted tests and docs 2013-08-01 18:41:13 +02:00
Jan Steemann a7c5350455 added server-id method 2013-08-01 18:27:42 +02:00
Jan Steemann c2611f567a bugfixed cap constraint 2013-08-01 13:17:38 +02:00
Jan Steemann 3b57e80241 simplified HTTP import API 2013-07-25 18:24:21 +02:00
Jan Steemann 9de2910717 updated replication documentation 2013-07-25 16:32:11 +02:00
Jan Steemann aa9845d1bd fixed graph test 2013-07-25 16:31:37 +02:00
Jan Steemann 8a254ea230 replication API documentation 2013-07-24 17:37:16 +02:00
Jan Steemann 4f14062d10 replication tests 2013-07-24 15:22:45 +02:00
Jan Steemann 3ab117de67 added collection.first() and collection.last() 2013-07-19 14:21:46 +02:00
Jan Steemann e359dc29dd INCOMPATIBLE CHANGE: changed AQL user function namespace resolution operator from `:` to `::` 
AQL user-defined functions were introduced in ArangoDB 1.3, and the namespace resolution
operator for them was the single colon (`:`). A function call looked like this:

    RETURN mygroup:myfunc()

The single colon caused an ambiguity in the AQL grammar, making it indistinguishable from
named attributes or the ternary operator in some cases, e.g.

    { mygroup:myfunc ? mygroup:myfunc }

The change of the namespace resolution operator from `:` to `::` fixes this ambiguity.

Existing user functions in the database will be automatically fixed when starting ArangoDB
1.4 with the `--upgrade` option. However, queries using user-defined functions need to be
adjusted on the client side to use the new operator.
 2013-07-18 12:02:28 +02:00
Jan Steemann 3cc4405c18 added collection.checksum() 2013-07-10 11:10:00 +02:00
Jan Steemann a07d2ea011 replication 2013-07-05 12:12:38 +02:00
Jan Steemann bb86a0b2d5 speed up simple queries testing 2013-06-28 09:54:20 +02:00
Jan Steemann db50b38370 fixed typos 2013-06-25 09:06:20 +02:00
Jan Steemann 373639a3b6 increase unittest timeout 2013-06-21 17:11:20 +02:00
Jan Steemann cae82f27e4 added `/_api/current-database` 2013-06-21 10:25:15 +02:00
Jan Steemann 9dfb7483ff "doCompact" attribute for collections 2013-06-19 16:51:16 +02:00
a-brandt 71c5f89010 Added unittests for structures 2013-06-18 15:56:01 +02:00
Jan Steemann 9599a021b9 moved some graph traversal validation into the traversal module 
- that simplifies some of the traversal-calling routines
- make returning error codes more consistent (specific 404 errors when
referring to unknown collections instead of simple 400 errors)
- optionally limit traversals to a certain number of iterations so they
  don't run endlessly in cyclic graphs
 2013-06-12 17:04:47 +02:00
Jan Steemann 212117d3b4 graph traversal API tests 2013-06-12 15:25:35 +02:00
Jan Steemann ede177aa55 issue #507, issue #508 2013-05-06 09:40:28 +02:00
Frank Celler 01d654e923 fixed https version of test 2013-05-05 23:34:02 +02:00
Frank Celler 48515d7bd8 fixed tests 2013-05-05 21:55:10 +02:00
Jan Steemann ee7ab712d6 issue #495 2013-05-03 11:08:58 +02:00
Jan Steemann ef1fcc89ee added test case for #491 2013-05-02 16:26:40 +02:00
Jan Steemann cd17f1ef44 issue #481 2013-04-21 11:37:46 +02:00
Jan Steemann 7d9777f8c5 extended API for user-defined AQL functions 2013-04-16 18:32:19 +02:00
Jan Steemann c945dbd2cd updated transaction API 2013-04-15 11:54:36 +02:00
Jan Steemann dee5adb9f5 added client side API for transactions 2013-04-12 23:18:48 +02:00
Frank Celler 3512fa6ff0 fixed error handling 2013-04-02 15:00:55 +02:00
Jan Steemann 55c1134702 replaced error code 9 2013-03-26 18:03:03 +01:00
Jan Steemann 6d82d45859 adjusted tests after Franks changes 2013-03-26 17:58:09 +01:00
Jan Steemann 69db58a154 index cleanup 2013-03-22 10:38:47 +01:00
Jan Steemann 40199d64b7 fixed handling of empty and reserved attribute names in documents 
specifying an empty attribute name in a document may have led to segmentation faults
when the document was unpacked later.
 2013-03-20 11:48:33 +01:00
Jan Steemann d54078390d fixed failing test 2013-03-19 14:57:11 +01:00
Jan Steemann 99522ccb84 switch order of insertion into indexes & datafile for updates 
updates are now done in the indexes first, then written to the datafile
 2013-03-18 13:03:05 +01:00
a-brandt b2703d4a49 fixed unittest 2013-03-13 14:46:55 +01:00
Jan Steemann 8ddf718c81 more detailed logging 2013-03-11 13:41:39 +01:00
a-brandt 4f6fbd9cd3 added more tests 2013-03-11 10:53:37 +01:00
a-brandt 1f4685a17d #412 added If-None-Match, If-Match and waitForSync 2013-03-08 17:00:15 +01:00
a-brandt e952b28aab changed http return codes for document update and delete 2013-03-08 16:56:15 +01:00
Jan Steemann 5631314bc7 issue #212: added auto-increment support for collections 
the feature can be used by creating a collection with the extra `keyOptions`
attribute as follows:

    db._create("mycollection", { keyOptions: { type: "autoincrement", offset: 1, increment: 10, allowUserKeys: true } });

The `type` attribute will make sure the keys will be auto-generated if no `_key` attribute is specified for a document.
The `allowUserKeys` attribute determines whether users might still supply own `_key` values with documents or if this
is considered an error.
The `increment` value determines the actual increment value, whereas the `offset` value can be used to seed to value
sequence with a specific starting value. This will be useful later in a multi-master setup, when multiple servers can use
different auto-increment seed values and thus generate non-conflicting auto-increment values.

The default values currently are:

- `allowUserKeys`: `true`
- `offset`: `0`
- `increment`: `1`

The only other available key generator type currently is `traditional`. The `traditional` key generator
will auto-generate keys in a fashion as ArangoDB always did (some increasing integer value, with a more or less unpredictable
increment value).

Note that for the `traditional` key generator there is no the option to disallow user-supplied keys and give the
server the sole responsibility for key generation.
 2013-03-08 11:54:03 +01:00
Frank Celler dd15025c1c fixed tests, add missing prefix = false to statistics call 2013-03-05 13:32:58 +01:00
Jan Steemann f32e5811d4 increase the http unittest timeout to make all tests pass even with Valgrind 2013-03-01 11:32:52 +01:00
Jan Steemann 47bce0a0b4 issue #436 2013-02-27 14:47:05 +01:00
Jan Steemann 13d1ff0057 issue #425 2013-02-22 23:43:52 +01:00
Jan Steemann 71459b680f issue #426 2013-02-22 23:26:52 +01:00
Jan Steemann 60349edaed fix for routing reload 2013-02-21 18:52:02 +01:00