arangodb

History

Alan Plum ae61d0e0e6 Fix TODOs in Foxx docs		2016-12-12 15:40:51 +01:00
..
Controllers	Docs: Use standard Markdown notation for headlines and disable MarkdownPP	2016-12-06 02:41:58 +01:00
Auth.mdpp	Fix TODOs in Foxx docs	2016-12-12 15:40:51 +01:00
Context.mdpp	Docs: Use standard Markdown notation for headlines and disable MarkdownPP	2016-12-06 02:41:58 +01:00
Manifest.mdpp	Docs: Use standard Markdown notation for headlines and disable MarkdownPP	2016-12-06 02:41:58 +01:00
Queries.mdpp	Docs: Use standard Markdown notation for headlines and disable MarkdownPP	2016-12-06 02:41:58 +01:00
README.mdpp	Docs: Use standard Markdown notation for headlines and disable MarkdownPP	2016-12-06 02:41:58 +01:00
Repositories.mdpp	Docs: Use standard Markdown notation for headlines and disable MarkdownPP	2016-12-06 02:41:58 +01:00
Sessions.mdpp	Docs: Use standard Markdown notation for headlines and disable MarkdownPP	2016-12-06 02:41:58 +01:00
Wayback.mdpp	Docs: Use standard Markdown notation for headlines and disable MarkdownPP	2016-12-06 02:41:58 +01:00

README.mdpp

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.

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).