1
0
Fork 0
arangodb/Documentation/Books/Manual/Foxx/Migrating2x
Mark a5b903e82c Documentation Foxx refactor (#5180) 2018-04-23 14:11:35 +02:00
..
Controllers Documentation Foxx refactor (#5180) 2018-04-23 14:11:35 +02:00
Auth.md Documentation Foxx refactor (#5180) 2018-04-23 14:11:35 +02:00
Context.md rename .mdpp files to .md so the handling is easier. 2017-05-04 12:04:24 +02:00
Manifest.md rename .mdpp files to .md so the handling is easier. 2017-05-04 12:04:24 +02:00
Queries.md Documentation Foxx refactor (#5180) 2018-04-23 14:11:35 +02:00
README.md Documentation Foxx refactor (#5180) 2018-04-23 14:11:35 +02:00
Repositories.md rename .mdpp files to .md so the handling is easier. 2017-05-04 12:04:24 +02:00
Sessions.md Documentation Foxx refactor (#5180) 2018-04-23 14:11:35 +02:00
Wayback.md rename .mdpp files to .md so the handling is easier. 2017-05-04 12:04:24 +02:00

README.md

Migrating 2.x services to 3.0

When migrating services from older versions of ArangoDB it is generally recommended you make sure they work in legacy compatibility mode, which can also serve as a stop-gap solution.

This chapter outlines the major differences in the Foxx API between ArangoDB 2.8 and ArangoDB 3.0.

General changes

The console object in later versions of ArangoDB 2.x implemented a special Foxx console API and would optionally log messages to a collection. ArangoDB 3.0 restores the original behaviour where console is the same object available from the console module.