mirror of https://gitee.com/bigwinds/arangodb
Correct typos in changelog and contributing doc
This commit is contained in:
CoDEmanX
parent
a39b712efe
commit
6e10811720
132
CHANGELOG
132
CHANGELOG
|
|
@ -219,7 +219,7 @@ v2.7.0 (XXXX-XX-XX)
|
|||
|
||||
* do not link arangoimp against V8
|
||||
|
||||
* AQL functon call arguments optimization
|
||||
* AQL function call arguments optimization
|
||||
|
||||
This will lead to arguments in function calls inside AQL queries will not be copied but passed
|
||||
by reference. This may speed up calls to functions with bigger argument values or queries that
|
||||
|
|
@ -245,9 +245,9 @@ v2.7.0 (XXXX-XX-XX)
|
|||
* the `skip()` function for simple queries does not accept negative input any longer.
|
||||
This feature was deprecated in 2.6.0.
|
||||
|
||||
* fix exeption handling
|
||||
* fix exception handling
|
||||
|
||||
In some cases javascript execptions would re-throw without information of the original problem.
|
||||
In some cases JavaScript exceptions would re-throw without information of the original problem.
|
||||
Now the original exception is logged for failure analysis.
|
||||
|
||||
* based REST API method PUT `/_api/simple/all` on the cursor API and make its use AQL internally.
|
||||
|
|
@ -285,7 +285,7 @@ v2.6.5 (XXXX-XX-XX)
|
|||
server default value for `indexBuckets` was used when restoring a collection.
|
||||
|
||||
* fixed "EscapeValue already set error" crash in V8 actions that might have occurred when
|
||||
cancelling V8-based operations.
|
||||
canceling V8-based operations.
|
||||
|
||||
|
||||
v2.6.4 (2015-08-01)
|
||||
|
|
@ -954,8 +954,8 @@ v2.6.0 (2015-06-20)
|
|||
|
||||
* Added the following JavaScript methods for file access:
|
||||
* fs.copyFile() to copy single files
|
||||
* fs.copyRecursive() to copy diretory trees
|
||||
* fs.chmod() to set the file permissions (non-Windows onnly)
|
||||
* fs.copyRecursive() to copy directory trees
|
||||
* fs.chmod() to set the file permissions (non-Windows only)
|
||||
|
||||
* Added process.env for accessing the process environment from JavaScript code
|
||||
|
||||
|
|
@ -1110,7 +1110,7 @@ v2.5.2 (2015-04-11)
|
|||
|
||||
* added `Foxx.Repository#exists`
|
||||
|
||||
* parallelise initialization of V8 context in multiple threads
|
||||
* parallelize initialization of V8 context in multiple threads
|
||||
|
||||
* fixed a possible crash when the debug-level was TRACE
|
||||
|
||||
|
|
@ -1169,7 +1169,7 @@ v2.5.1 (2015-03-19)
|
|||
collections from happening.
|
||||
|
||||
* datafiles and `parameter.json` files written by arangod are now created with read and write
|
||||
privileges for the arangod process user, and with read and write prileges for the arangod
|
||||
privileges for the arangod process user, and with read and write privileges for the arangod
|
||||
process group.
|
||||
|
||||
Previously, these files were created with user read and write permissions only.
|
||||
|
|
@ -1192,7 +1192,7 @@ v2.5.1 (2015-03-19)
|
|||
|
||||
* add system error strings for Windows on many places
|
||||
|
||||
* rework service startup so we anounce 'RUNNING' only when we're finished starting.
|
||||
* rework service startup so we announce 'RUNNING' only when we're finished starting.
|
||||
|
||||
* use the Windows eventlog for FATAL and ERROR - log messages
|
||||
|
||||
|
|
@ -1270,8 +1270,8 @@ v2.5.0-beta2 (2015-02-23)
|
|||
* Rewrite of Foxx routing
|
||||
|
||||
The routing of Foxx has been exposed to major internal changes we adjusted because of user feedback.
|
||||
This allows us to set the development mode per mountpoint without having to change pathes and hold
|
||||
apps at seperate locations.
|
||||
This allows us to set the development mode per mountpoint without having to change paths and hold
|
||||
apps at separate locations.
|
||||
|
||||
* Foxx Development mode
|
||||
|
||||
|
|
@ -1301,7 +1301,7 @@ v2.5.0-beta2 (2015-02-23)
|
|||
|
||||
Until 2.4 the errors produced by Foxx were not optimal. Often, the error message was just
|
||||
`unable to parse manifest` and contained only an internal stack trace.
|
||||
In 2.5 we made major improvements there, including a much more finegrained error output that
|
||||
In 2.5 we made major improvements there, including a much more fine-grained error output that
|
||||
helps you debug your Foxx apps. The error message printed is now much closer to its source and
|
||||
should help you track it down.
|
||||
|
||||
|
|
@ -1408,7 +1408,7 @@ v2.5.0-beta2 (2015-02-23)
|
|||
will not make use of a sparse index in a query in order to produce correct results.
|
||||
|
||||
For example, the following queries cannot use a sparse index on `attr` because the optimizer
|
||||
will not know beforehand whether the comparsion values for `doc.attr` will include `null`:
|
||||
will not know beforehand whether the comparison values for `doc.attr` will include `null`:
|
||||
|
||||
FOR doc In collection
|
||||
FILTER doc.attr == SOME_FUNCTION(...)
|
||||
|
|
@ -1428,7 +1428,7 @@ v2.5.0-beta2 (2015-02-23)
|
|||
|
||||
Executing the two in lockstep allows using much smaller buffers for intermediate results
|
||||
and starts the actual data-modification operations much earlier than if the two phases
|
||||
were executed seperately.
|
||||
were executed separately.
|
||||
|
||||
* Allow dynamic attribute names in AQL object literals
|
||||
|
||||
|
|
@ -1452,7 +1452,7 @@ v2.5.0-beta2 (2015-02-23)
|
|||
|
||||
FOR doc IN collection FILTER doc.value1 == 1 && doc.value2 == 2 SORT doc.value1, doc.value2 RETURN doc
|
||||
|
||||
* make AQL optimizer rule "use-index-for-sort" remove sort also in case the sort critieria
|
||||
* make AQL optimizer rule "use-index-for-sort" remove sort also in case the sort criteria
|
||||
excludes the left-most index attributes, but the left-most index attributes are used
|
||||
by the index for equality-only lookups.
|
||||
|
||||
|
|
@ -1572,7 +1572,7 @@ v2.4.6 (2015-03-18)
|
|||
collections from happening.
|
||||
|
||||
* datafiles and `parameter.json` files written by arangod are now created with read and write
|
||||
privileges for the arangod process user, and with read and write prileges for the arangod
|
||||
privileges for the arangod process user, and with read and write privileges for the arangod
|
||||
process group.
|
||||
|
||||
Previously, these files were created with user read and write permissions only.
|
||||
|
|
@ -1694,7 +1694,7 @@ v2.4.2 (2015-01-30)
|
|||
It will not state any information about your Application.
|
||||
Before it was a 404 Not Found without any information and not distinguishable from a correct not found on your route.
|
||||
|
||||
In Development Mode the html page also contains information about the error occured.
|
||||
In Development Mode the html page also contains information about the error occurred.
|
||||
|
||||
* Unhandled errors thrown in Foxx routes are now handled by the Foxx framework itself.
|
||||
|
||||
|
|
@ -1815,7 +1815,7 @@ v2.4.0-beta1 (2014-12-26)
|
|||
* download links
|
||||
* API documentation
|
||||
|
||||
To install a new application, a new dialogue is now available.
|
||||
To install a new application, a new dialog is now available.
|
||||
It provides the features already available in the console application `foxx-manager` plus some more:
|
||||
* install an application from Github
|
||||
* install an application from a zip file
|
||||
|
|
@ -1933,10 +1933,10 @@ v2.4.0-beta1 (2014-12-26)
|
|||
* replication.applier.properties({ includeSystem: false });
|
||||
|
||||
This will exclude all system collections (including `_aqlfunctions`, `_graphs` etc.)
|
||||
from the initial synchronisation and the continuous replication.
|
||||
from the initial synchronization and the continuous replication.
|
||||
|
||||
If this is also undesired, it is also possible to specify a list of collections to
|
||||
exclude from the initial synchronisation and the continuous replication using the
|
||||
exclude from the initial synchronization and the continuous replication using the
|
||||
`restrictCollections` attribute, e.g.:
|
||||
|
||||
replication.applier.properties({
|
||||
|
|
@ -1993,7 +1993,7 @@ v2.3.4 (2014-12-23)
|
|||
v2.3.3 (2014-12-17)
|
||||
-------------------
|
||||
|
||||
* fixed error handling in instanciation of distributed AQL queries, this
|
||||
* fixed error handling in instantiation of distributed AQL queries, this
|
||||
also fixes a bug in cluster startup with many servers
|
||||
|
||||
* issue #1185: parse non-fractional JSON numbers with exponent (e.g. `4e-261`)
|
||||
|
|
@ -2087,7 +2087,7 @@ v2.3.0 (2014-11-18)
|
|||
* fixed syslog flags. `--log.syslog` is deprecated and setting it has no effect,
|
||||
`--log.facility` now works as described. Application name has been changed from
|
||||
`triagens` to `arangod`. It can be changed using `--log.application`. The syslog
|
||||
will only contain the actual log message. The datetime prefix is omiited.
|
||||
will only contain the actual log message. The datetime prefix is omitted.
|
||||
|
||||
* fixed deflate in SimpleHttpClient
|
||||
|
||||
|
|
@ -2161,7 +2161,7 @@ v2.3.0-beta2 (2014-11-08)
|
|||
* fixed issue #1075: Aardvark: user name required even if auth is off #1075
|
||||
|
||||
The fix for this prefills the username input field with the current user's
|
||||
accout name if any and `root` (the default username) otherwise. Additionally,
|
||||
account name if any and `root` (the default username) otherwise. Additionally,
|
||||
the tooltip text has been slightly adjusted.
|
||||
|
||||
* fixed issue #1069: Add 'raw' link to swagger ui so that the raw swagger
|
||||
|
|
@ -2243,7 +2243,7 @@ v2.3.0-beta1 (2014-11-01)
|
|||
thus been removed in ArangoDB 2.3. It is not possible to create indexes of type
|
||||
"bitarray" with ArangoDB 2.3.
|
||||
|
||||
When a collection is openend that contains a bitarray index definition created
|
||||
When a collection is opened that contains a bitarray index definition created
|
||||
with a previous version of ArangoDB, ArangoDB will ignore it and log the following
|
||||
warning:
|
||||
|
||||
|
|
@ -2381,7 +2381,7 @@ v2.3.0-beta1 (2014-11-01)
|
|||
|
||||
* front-end: now using the new graph api including multi-collection support
|
||||
|
||||
* front-end: foxx apps are now deleteable
|
||||
* front-end: foxx apps are now deletable
|
||||
|
||||
* front-end: foxx apps are now installable and updateable through github, if github is their
|
||||
origin.
|
||||
|
|
@ -2886,7 +2886,7 @@ v2.2.0 (2014-07-10)
|
|||
|
||||
Cross-collection transactions in ArangoDB should benefit considerably by this
|
||||
change, as less writes than in previous versions are required to ensure the data
|
||||
of multiple collections are atomcially and durably committed. All data-modifying
|
||||
of multiple collections are atomically and durably committed. All data-modifying
|
||||
operations inside transactions (insert, update, remove) will write their
|
||||
operations into the write-ahead log directly, making transactions with multiple
|
||||
operations also require less physical memory than in previous versions of ArangoDB,
|
||||
|
|
@ -3062,7 +3062,7 @@ v2.1.0-rc1 (XXXX-XX-XX)
|
|||
the previous undocumented function `internal.definePeriodic` is now
|
||||
deprecated and will be removed in a future release.
|
||||
|
||||
* decrease the size of some seldomly used system collections on creation.
|
||||
* decrease the size of some seldom used system collections on creation.
|
||||
|
||||
This will make these collections use less disk space and mapped memory.
|
||||
|
||||
|
|
@ -3139,7 +3139,7 @@ v2.1.0-rc1 (XXXX-XX-XX)
|
|||
* added REST API method HTTP GET `/_api/job/job-id` to query the status of an
|
||||
async job without potentially fetching it from the list of done jobs
|
||||
|
||||
* fixed non-intuitive behaviour in jobs API: previously, querying the status
|
||||
* fixed non-intuitive behavior in jobs API: previously, querying the status
|
||||
of an async job via the API HTTP PUT `/_api/job/job-id` removed a currently
|
||||
executing async job from the list of queryable jobs on the server.
|
||||
Now, when querying the result of an async job that is still executing,
|
||||
|
|
@ -3222,7 +3222,7 @@ v2.0.5 (2014-04-21)
|
|||
|
||||
* Fixed a caching problem in IE JS Shell
|
||||
|
||||
* added cancelation for async jobs
|
||||
* added cancellation for async jobs
|
||||
|
||||
* upgraded to new gyp for V8
|
||||
|
||||
|
|
@ -3555,9 +3555,9 @@ v1.4.16 (XXXX-XX-XX)
|
|||
v1.4.15 (2014-04-19)
|
||||
--------------------
|
||||
|
||||
* bugfix for AQL query optimiser
|
||||
* bugfix for AQL query optimizer
|
||||
|
||||
the following type of query was too eagerly optimised, leading to errors in code-generation:
|
||||
the following type of query was too eagerly optimized, leading to errors in code-generation:
|
||||
|
||||
LET a = (FOR i IN [] RETURN i) LET b = (FOR i IN [] RETURN i) RETURN 1
|
||||
|
||||
|
|
@ -3570,7 +3570,7 @@ v1.4.14 (2014-04-05)
|
|||
|
||||
* fixed race conditions during shape / attribute insertion
|
||||
|
||||
A race condition could have led to spurios `cannot find attribute #xx` or
|
||||
A race condition could have led to spurious `cannot find attribute #xx` or
|
||||
`cannot find shape #xx` (where xx is a number) warning messages being logged
|
||||
by the server. This happened when a new attribute was inserted and at the same
|
||||
time was queried by another thread.
|
||||
|
|
@ -3579,7 +3579,7 @@ v1.4.14 (2014-04-05)
|
|||
access the shapes / attributes hash tables while they were resized. In this
|
||||
cases, the shape / attribute may have been hashed to a wrong slot.
|
||||
|
||||
* fixed a memory barrier / cpu synchronisation problem with libev, affecting
|
||||
* fixed a memory barrier / cpu synchronization problem with libev, affecting
|
||||
Windows with Visual Studio 2013 (probably earlier versions are affected, too)
|
||||
|
||||
The issue is described in detail here:
|
||||
|
|
@ -3642,9 +3642,9 @@ v1.4.11 (2014-02-27)
|
|||
|
||||
* fixed bug in Graph.pathTo function
|
||||
|
||||
* fixed small memleak in AQL optimiser
|
||||
* fixed small memleak in AQL optimizer
|
||||
|
||||
* fixed access to potentially uninitialised variable when collection had a cap constraint
|
||||
* fixed access to potentially uninitialized variable when collection had a cap constraint
|
||||
|
||||
|
||||
v1.4.10 (2014-02-21)
|
||||
|
|
@ -3707,7 +3707,7 @@ v1.4.9 (2014-02-07)
|
|||
RETURN doc
|
||||
|
||||
The function requires a skiplist index with the exact same attributes to
|
||||
be present on the specified colelction. All attributes present in the skiplist
|
||||
be present on the specified collection. All attributes present in the skiplist
|
||||
index must be specified in the conditions specified for the `SKIPLIST` function.
|
||||
Attribute declaration order is important, too: attributes must be specified in the
|
||||
same order in the condition as they have been declared in the skiplist index.
|
||||
|
|
@ -3874,7 +3874,7 @@ v1.4.4 (2013-12-24)
|
|||
v1.4.3 (2013-11-25)
|
||||
-------------------
|
||||
|
||||
* fixed a segfault in the AQL optimiser, occurring when a constant non-list value was
|
||||
* fixed a segfault in the AQL optimizer, occurring when a constant non-list value was
|
||||
used on the right-hand side of an IN operator that had a collection attribute on the
|
||||
left-hand side
|
||||
|
||||
|
|
@ -3913,7 +3913,7 @@ v1.4.2 (2013-11-20)
|
|||
|
||||
* fixed startup of server in daemon mode (`--daemon` startup option)
|
||||
|
||||
* fixed a segfault in the AQL optimiser
|
||||
* fixed a segfault in the AQL optimizer
|
||||
|
||||
* issue #671: Method graph.measurement does not exist
|
||||
|
||||
|
|
@ -3996,7 +3996,7 @@ v1.4.1-rc1 (2013-11-07)
|
|||
|
||||
* fixed issue #653: Slow query
|
||||
|
||||
* fixed issue #650: Randonmess of any() should be improved
|
||||
* fixed issue #650: Randomness of any() should be improved
|
||||
|
||||
* made AQL `DOCUMENT()` function polymorphic and work with just one parameter.
|
||||
|
||||
|
|
@ -4036,7 +4036,7 @@ v1.4.1-rc1 (2013-11-07)
|
|||
v1.4.0 (2013-10-29)
|
||||
-------------------
|
||||
|
||||
* fixed issue #648: /batch API is missing from Web Interface API Docummentation (Swagger)
|
||||
* fixed issue #648: /batch API is missing from Web Interface API Documentation (Swagger)
|
||||
|
||||
* fixed issue #647: Icon tooltips missing
|
||||
|
||||
|
|
@ -4102,7 +4102,7 @@ v1.4.0 (2013-10-29)
|
|||
|
||||
* added function to manage indexes (web interface)
|
||||
|
||||
* improved server shutdown time by signalling shutdown to applicationserver,
|
||||
* improved server shutdown time by signaling shutdown to applicationserver,
|
||||
logging, cleanup and compactor threads
|
||||
|
||||
* added foxx-manager `replace` command
|
||||
|
|
@ -4170,7 +4170,7 @@ v1.4.0-beta2 (2013-10-14)
|
|||
name of a collection for each replication event.
|
||||
|
||||
The replication applier will now look for the collection name attribute in logged
|
||||
events preferrably.
|
||||
events preferably.
|
||||
|
||||
* added database selection to arango-dfdb
|
||||
|
||||
|
|
@ -4206,7 +4206,7 @@ v1.4.0-beta2 (2013-10-14)
|
|||
the import completely fail if at least one of documents cannot be imported successfully.
|
||||
|
||||
It defaults to `false`, which will make ArangoDB continue importing the other documents
|
||||
from the import even if some documents cannot be imported. This is the same behaviour that
|
||||
from the import even if some documents cannot be imported. This is the same behavior that
|
||||
previous ArangoDB versions exposed.
|
||||
|
||||
* added missing swagger documentation for `/_api/log`
|
||||
|
|
@ -4307,7 +4307,7 @@ v1.4.0-beta1 (2013-10-01)
|
|||
|
||||
arangorestore can be used to restore data from a dump created with arangodump.
|
||||
arangorestore currently does not re-create any indexes, and doesn't yet handle
|
||||
referenced documents in edges propertly when doing just partial restores.
|
||||
referenced documents in edges properly when doing just partial restores.
|
||||
This will be fixed until 1.4 stable.
|
||||
|
||||
* introduced `--server.database` option for arangosh, arangoimp, and arangob.
|
||||
|
|
@ -4768,7 +4768,7 @@ v1.4.0-alpha1 (2013-08-02)
|
|||
|
||||
* issue #523: Graph and vertex methods for the javascript api
|
||||
|
||||
* issue #517: Foxx: Route parameters with captial letters fail
|
||||
* issue #517: Foxx: Route parameters with capital letters fail
|
||||
|
||||
* issue #512: Binded Parameters for LIMIT
|
||||
|
||||
|
|
@ -4961,7 +4961,7 @@ v1.3.alpha1 (2013-04-05)
|
|||
required.
|
||||
|
||||
* added AQL functions VARIANCE_POPULATION(), VARIANCE_SAMPLE(), STDDEV_POPULATION(),
|
||||
STDDEV_SAMPLE(), AVERAGE(), MEDIAN() to calculate stastical values for lists
|
||||
STDDEV_SAMPLE(), AVERAGE(), MEDIAN() to calculate statistical values for lists
|
||||
|
||||
* added AQL SQRT() function
|
||||
|
||||
|
|
@ -5002,7 +5002,7 @@ v1.2.3 (XXXX-XX-XX)
|
|||
|
||||
* fixed firstExample() query with `_id` and `_key` attributes
|
||||
|
||||
* issue triAGENS/ArangoDB-PHP#55: AQL optimiser may have mis-optimised duplicate
|
||||
* issue triAGENS/ArangoDB-PHP#55: AQL optimizer may have mis-optimized duplicate
|
||||
filter statements with limit
|
||||
|
||||
|
||||
|
|
@ -5283,7 +5283,7 @@ v1.2.beta1 (2013-02-01)
|
|||
additionally return the number of shapes used in the collection in the
|
||||
extra attribute "shapes.count"
|
||||
|
||||
* added AQL TRAVERSAL_TREE() function to return a hierchical result from a traversal
|
||||
* added AQL TRAVERSAL_TREE() function to return a hierarchical result from a traversal
|
||||
|
||||
* added AQL TRAVERSAL() function to return the results from a traversal
|
||||
|
||||
|
|
@ -5380,11 +5380,11 @@ v1.2.beta1 (2013-02-01)
|
|||
|
||||
* issue #338: arangosh cursor positioning problems
|
||||
|
||||
* issue #326: use limit optimisation with filters
|
||||
* issue #326: use limit optimization with filters
|
||||
|
||||
* issue #325: use index to avoid sorting
|
||||
|
||||
* issue #324: add limit optimisation to AQL
|
||||
* issue #324: add limit optimization to AQL
|
||||
|
||||
* removed arango-password script and added Javascript functionality to add/delete
|
||||
users instead. The functionality is contained in module `users` and can be invoked
|
||||
|
|
@ -5440,7 +5440,7 @@ v1.2.beta1 (2013-02-01)
|
|||
* any other characters, especially multi-byte sequences, whitespace or
|
||||
punctuation characters cannot be used inside key values
|
||||
|
||||
Specifiying a document key is optional when creating new documents. If no
|
||||
Specifying a document key is optional when creating new documents. If no
|
||||
document key is specified, ArangoDB will create a document key itself.
|
||||
There are no guarantees about the format and pattern of auto-generated document
|
||||
keys other than the above restrictions.
|
||||
|
|
@ -5506,7 +5506,7 @@ v1.1.3 (2013-XX-XX)
|
|||
|
||||
* fixed issue #379: arango-password fatal issue javscript.startup-directory
|
||||
|
||||
* fixed issue #372: Command-Line Options for the Authentication and Authorisation
|
||||
* fixed issue #372: Command-Line Options for the Authentication and Authorization
|
||||
|
||||
|
||||
v1.1.2 (2013-01-20)
|
||||
|
|
@ -5662,7 +5662,7 @@ v1.1.0 (2012-12-05)
|
|||
|
||||
* fixed issue #281: documentation for skip lists shows wrong example
|
||||
|
||||
* fixed AQL optimiser bug, related to OR-combined conditions that filtered on the
|
||||
* fixed AQL optimizer bug, related to OR-combined conditions that filtered on the
|
||||
same attribute but with different conditions
|
||||
|
||||
* fixed issue #277: allow usage of collection names when creating edges
|
||||
|
|
@ -5682,7 +5682,7 @@ v1.1.beta2 (2012-11-13)
|
|||
v1.1.beta1 (2012-10-24)
|
||||
-----------------------
|
||||
|
||||
* fixed AQL optimiser bug
|
||||
* fixed AQL optimizer bug
|
||||
|
||||
* WARNING:
|
||||
- the user has changed from "arango" to "arangodb", the start script has changed from
|
||||
|
|
@ -5716,9 +5716,9 @@ v1.1.beta1 (2012-10-24)
|
|||
and will close the connection if the client does not send the remaining data
|
||||
|
||||
- if Content-Length is bigger than the maximum allowed size (512 MB), the server will
|
||||
fail with HTTP 413 (request entitiy too large).
|
||||
fail with HTTP 413 (request entity too large).
|
||||
|
||||
- if the length of the HTTP headers is greated than the maximum allowed size (1 MB),
|
||||
- if the length of the HTTP headers is greater than the maximum allowed size (1 MB),
|
||||
the server will fail with HTTP 431 (request header fields too large)
|
||||
|
||||
* issue #265: allow optional base64 encoding/decoding of action response data
|
||||
|
|
@ -5730,7 +5730,7 @@ v1.1.beta1 (2012-10-24)
|
|||
--javascript.v8-options. Using this option, the Harmony features or other settings in
|
||||
v8 can be enabled if the end user requires them
|
||||
|
||||
* issue #248: allow AQL optimiser to pull out completely uncorrelated subqueries to the
|
||||
* issue #248: allow AQL optimizer to pull out completely uncorrelated subqueries to the
|
||||
top level, resulting in less repeated evaluation of the subquery
|
||||
|
||||
* upgraded to Doxygen 1.8.0
|
||||
|
|
@ -5765,9 +5765,9 @@ v1.1.beta1 (2012-10-24)
|
|||
|
||||
* issue #219: continue in case of "document not found" error in PATHS() function
|
||||
|
||||
* issue #213: make waitForSync overridable on specifc actions
|
||||
* issue #213: make waitForSync overridable on specific actions
|
||||
|
||||
* changed AQL optimiser to use indexes in more cases. Previously, indexes might
|
||||
* changed AQL optimizer to use indexes in more cases. Previously, indexes might
|
||||
not have been used when in a reference expression the inner collection was
|
||||
specified last. Example: FOR u1 IN users FOR u2 IN users FILTER u1._id == u2._id
|
||||
Previously, this only checked whether an index could be used for u2._id (not
|
||||
|
|
@ -5776,7 +5776,7 @@ v1.1.beta1 (2012-10-24)
|
|||
above as above, indexes are checked for both sides.
|
||||
|
||||
* issue #204: extend the CSV import by TSV and by user configurable
|
||||
seperator character(s)
|
||||
separator character(s)
|
||||
|
||||
* issue #180: added support for batch operations
|
||||
|
||||
|
|
@ -5885,7 +5885,7 @@ v1.0.4 (2012-11-12)
|
|||
v1.0.3 (2012-11-08)
|
||||
-------------------
|
||||
|
||||
* fixed AQL optimiser bug
|
||||
* fixed AQL optimizer bug
|
||||
|
||||
* issue #273: fixed segfault in arangosh on HTTP 40x
|
||||
|
||||
|
|
@ -5991,7 +5991,7 @@ v1.0.beta3 (2012-08-10)
|
|||
if set to false, shape data is synched to disk if waitForSync for the collection is
|
||||
set to true, otherwise, shape data is not synched.
|
||||
|
||||
* fix for issue #145: strange issue on Travis: added epsilon for numeric comparion in
|
||||
* fix for issue #145: strange issue on Travis: added epsilon for numeric comparison in
|
||||
geo index
|
||||
|
||||
* fix for issue #136: adjusted message during indexing
|
||||
|
|
@ -6023,7 +6023,7 @@ v1.0.beta1 (2012-07-29)
|
|||
for arangosh and arangoimp to "--server.connect-timeout" and "--server.request-timeout"
|
||||
|
||||
* INCOMPATIBLE CHANGE: authorization is now required on the server side
|
||||
Clients sending requests without HTTP autorization will be rejected with HTTP 401
|
||||
Clients sending requests without HTTP authorization will be rejected with HTTP 401
|
||||
To allow backwards compatibility, the server can be started with the option
|
||||
"--server.disable-authentication"
|
||||
|
||||
|
|
@ -6081,7 +6081,7 @@ v1.0.beta1 (2012-07-29)
|
|||
"keep-alive" if the request was an HTTP/1.1 request, and "close" if the
|
||||
request was an HTTP/1.0 request
|
||||
|
||||
* (minimal) internal optimisations for HTTP request parsing and response header
|
||||
* (minimal) internal optimizations for HTTP request parsing and response header
|
||||
handling
|
||||
|
||||
* fixed Unicode unescaping bugs for \f and surrogate pairs in BasicsC/strings.c
|
||||
|
|
@ -6159,9 +6159,9 @@ v1.0.alpha2 (2012-06-24)
|
|||
|
||||
* added option SKIP_RANGES=1 for make unittests
|
||||
|
||||
* fixed several range-related assertion failures in the AQL query optimiser
|
||||
* fixed several range-related assertion failures in the AQL query optimizer
|
||||
|
||||
* fixed AQL query optimisations for some edge cases (e.g. nested subqueries with
|
||||
* fixed AQL query optimizations for some edge cases (e.g. nested subqueries with
|
||||
invalid constant filter expressions)
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -57,8 +57,8 @@ Making Changes
|
|||
|
||||
* Develop and test your modifications there
|
||||
|
||||
* Commit as you like, but preferrably in logical chunks. Use meaningful commit
|
||||
messages and make sure you do not commit unneccesary files (e.g. object
|
||||
* Commit as you like, but preferably in logical chunks. Use meaningful commit
|
||||
messages and make sure you do not commit unnecessary files (e.g. object
|
||||
files). It is normally a good idea to reference the issue number from the
|
||||
commit message so the issues will get updated automatically with comments.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue