1
0
Fork 0
arangodb/Documentation/Books/Manual/Foxx/Migrating2x
Alan Plum 554a4f7ae3
Split up Foxx migration docs
2016-06-23 16:09:46 +02:00
..
Controllers Split up Foxx migration docs 2016-06-23 16:09:46 +02:00
Auth.mdpp Split up Foxx migration docs 2016-06-23 16:09:46 +02:00
Context.mdpp Split up Foxx migration docs 2016-06-23 16:09:46 +02:00
Manifest.mdpp Split up Foxx migration docs 2016-06-23 16:09:46 +02:00
Queries.mdpp Split up Foxx migration docs 2016-06-23 16:09:46 +02:00
README.mdpp Split up Foxx migration docs 2016-06-23 16:09:46 +02:00
Repositories.mdpp Split up Foxx migration docs 2016-06-23 16:09:46 +02:00
Sessions.mdpp Split up Foxx migration docs 2016-06-23 16:09:46 +02:00
Wayback.mdpp Split up Foxx migration docs 2016-06-23 16:09:46 +02:00

README.mdpp

!CHAPTER 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](../LegacyMode.md), 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.

!SECTION 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](../../Appendix/JavaScriptModules/Console.md).