Projects / OrientDB / Releases

All releases of OrientDB

  •  29 Jul 2010 15:46
Avatar

    Release Notes: A new GraphDB implementation. Import and export of the database in JSON format. A new Connection Pool, Support for lazy loaded collections and maps. A new Fetch Plan to optimize transfer between the client and server. SQL access to the record attributes. A new Logging config. New console commands (import database, export database, create class, and compare database). New annotations to control object mapping: ORawBinding, ODocumentId, and ODocumentInstance. Reached 240 unit tests. Fixes for many bugs (see the issue tracker).

    •  12 Jul 2010 16:27
    Avatar

      Release Notes: New run-time Fetch Plans to choose the fetching strategy at run-time. New database properties. POJO callbacks on serialization/deserialization. New annotation to use RAW binding. Fixes for object graph management and minor bugs.

      •  25 Jun 2010 16:23
      Avatar

        Release Notes: Support for native inheritance between Documents and POJOs. Implementation of non-unique indexes. Support for ORDER BY clause in SQL SELECT statements. Improved description on errors. Auto-registration of Remote Engine, if available. Fixes for other bugs (user loading and logical cluster casts).

        •  21 Jun 2010 12:11
        Avatar

          Release Notes: The "create link" SQL command was added to create a physical connection between records. This can be useful when importing a relational DBMS. The "inverse" form can be used to map 1-N relationships. The "import documents" console command was added to import a JSON document. The SQL command "create property" was added to add schema full properties. Status was added in OUser and checked upon login. By default, it is ACTIVE. Support of ORID in queries was implemented. Other bugs were fixed.

          •  07 Jun 2010 08:13
          Avatar

            Release Notes: An Index API was added to create unique indexes at the property level. This speeds up the performance of queries but slows down updates, inserts, and deletes. OrientDB Studio has new rendering for links. A bug regarding embedded type in collections was fixed.

            •  31 May 2010 11:29
            Avatar

              Release Notes: A new hook API was added. This is like triggers of an RDBMS, but it calls Java application code. All the bugs reported by the users in the last few weeks were fixed.

              •  28 May 2010 11:53
              Avatar

                Release Notes: This release adds new management of users and roles, the new SQL commands GRANT and REVOKE to manage permissions, enforced security in OrientDB Server with the support of Server users, fixes for minor issues, and *.config files changed to *.xml. The Server administrator account is now created at first start of the Server with a random password.

                •  21 May 2010 14:25
                Avatar

                  Release Notes: This release adds a new Database structure, integrates logical clusters well at the storage level, improves OrientDB Studio with authentication, users, roles, clusters, db and server properties, etc., adds new User and Role management, adds more flexible management of types in ODocument instances, supports HTTP basic authentication, and fixes some bugs in concurrency with a high number of clients.

                  •  10 May 2010 07:51
                  Avatar

                    Release Notes: An HTTP RESTful interface was added to the OrientDB Server. The OrientDB Server Studio GUI was added to manage documents and requests and to monitor the active connections. It's a client-side Web application built with HTML, CSS, and jQuery. Minor bugs on HTTP connections were fixed.

                    •  05 May 2010 11:52
                    Avatar

                      Release Notes: Full support was added for asynchronous remote command execution. All SQL commands can be executed remotely (select, insert, update, delete). A bug regarding the LIKE operator was fixed. JMX monitoring support was improved for OrientDB Server: active sessions, configured handlers and protocols, status, etc. The default OrientDB Server port was changed to 2424. OrientKV Server has been assigned the port number 2431.

                      Screenshot

                      Project Spotlight

                      episoder

                      A tool to tell you about new episodes of your favourite TV shows.

                      Screenshot

                      Project Spotlight

                      BalanceNG

                      A modern software IP load balancer.