© 2006-2012 Radicore Software Ltd
Latest news
RADICORE v1.72.0 released10 December 2011
RADICORE v1.71.0 released02 September 2011
RADICORE v1.70.0 released25 August 2011
Knowledge Base
The use of Cascading Style Sheets within Radicore22 April 2008
How to implement Two Factor Authentication01 February 2008
How to implement a Virtual Private Database01 October 2007
Articles
Creating an SQL Server driver for RADICORE01 January 2011
Using Radicore components in a front-end website01 June 2009
Web Site vs Web Application01 September 2008
Other Stuff
Not-so-SOLID OO Principles08 June 2011
Dependency Injection is EVIL03 June 2011
Object Relational Mappers are EVIL20 August 2007
Radicore for PHP
Radicore has been tested with the following versions of PHP:
- PHP 4.3.8 and above, with the following extensions:
- DOM XML for creating the XML documents.
- Sablotron XSLT for performing XSL transformations.
- MultiByte String if it is required to deal with UTF-8 character sets.
- PHP 5.0.0 and above, with the following extensions:
- DOM for creating the XML documents.
- XSL for performing XSL transformations.
- MultiByte String if it is required to deal with UTF-8 character sets.
You do not have to tell the code which version to use as it is clever enough to work it out for itself. You do, however, have to ensure that all required extensions are available.
The following database drivers are also included:
- MySQL version 4.0.6 to 4.0.25, which uses the original MySQL extension. Note that MySQL stopped active support for version 4.0 on 30th September 2006.
- MySQL version 4.1 and above, which uses the improved MySQL extension. Note that MySQL stopped active support for version 4.1 on 31st December 2006.
- PostgreSQL version 8 and above.
- Oracle 10g
- SQL Server 2008 R2
When the database supplier terminates active support for a particular version of their product it also means that there can be no guarantee that Radicore will function on that unsupported, obsolete version. Radicore uses features which are available in the current version of the database, so it may cease to function if used with an older version of the database in which those features do not exist.
Although you have to define in the CONFIG.INC file which RDBMS you are using - MySQL, PostgreSQL, Oracle or SQL Server - there are different class files available for MySQL and Oracle due to different API names with different versions. There is no need to specify which class file to use as the framework is clever enough to work it out for itself.
The software has been built and tested using the Apache web server. No guarantees can be given regarding the reliability or performance with other web servers.
Follow this link for the downloads page.