• The “full release” link gives you a new empty V5 system and please note that it is not possible to import developments from a V4 system into V5.
• The “ebase upgrade” link provides the ability to upgrade an existing V4 system to V5 – this is a one-way process and you won’t be able to go back once you’ve completed the upgrade, so please be sure to only perform an upgrade on a copy of an existing system – this copy should include a copy of the repository database. The upgrade procedure is largely manual with lots of steps – it will probably take around 15 mins to complete.
http://www.ebaseftp.com/download/ebase_ ... 0_beta.zip
http://www.ebaseftp.com/download/ebase_ ... 06Beta.zip
Please report any issues/suggestions/questions etc using the Version 5 Beta section of this forum.
Here is a summary of the main changes introduced in V5.0:
- 1. In V5.0, all objects created in the designer are saved as files in a local workspace instead of to the Repository Database as was the case with V4.0. This makes it possible to use a source control system such as CVS or SVN.
2. Entities created in the designer can be saved anywhere in the workspace.
3. Web Resource files such as images, style sheets, HTML files etc can now be created and edited using the designer and are saved in the workspace.
4. A new deployment capability has been introduced that makes it much easier to deploy new applications and changes to target servers.
5. All named elements e.g. entities, fields, tables, pages etc. are now case sensitive. The FPL scripting language remains case insensitive, Javascript is case sensitive.
6 Referential integrity for all relationships is much improved. This includes display of referencing information and automatic refactoring.
7. The designer and server components have been separated: these two components can largely exist independently of each other. In particular, the designer can be started without a server.
8. Introduction of an integrated test server (this is an option) within the designer. This is started/stopped automatically with the designer and is largely invisible to the designer user.
9. Introduction of a new Server Administration Application to perform all server admin.