Trace: • credits • 1.0 • howto • telechargement • erreurs-1.1 • 1.8 • 1.2.x
Differences ¶
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| en:tutorial:using-dao [2007/01/13 21:28] – created doubleface | en:tutorial:using-dao [2007/09/17 22:42] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== How to use daos ====== | + | This page has been moved to [[en:tutorials:main: |
| - | + | ||
| - | Jelix proposes a relational object-mapping system named jDao, based on DAO pattern. | + | |
| - | + | ||
| - | The DAO pattern is based on two types of objects | + | |
| - | + | ||
| - | + | ||
| - | Concretely with jDao, a DAO XML file enables you to define a record and a factory, which will act on one or more tables at the same time. You thus define the mapping in it: which field of the table will go in which property of the record, as well as the type of data, the keys, on which tables the mapping is carried out, according to which joints etc. | + | |
| - | + | ||
| - | + | ||
| - | Starting from this file, jDao dynamically generates two classes based respectively on jDaoRecordBase and jDaoFactoryBase (which is stored in a php file in the cache of jelix), in which all main methods and SQL requests are **statically** provided. Indeed, in contrary to other mapping systems, SQL requests are thus generated only once, and not dynamically with each page calls That allows better performances. | + | |
| - | + | ||
| - | In the DAO XML file, you can also define your own access methods to data, and jDao will generate the corresponding methods and requests in the DAO factory. | + | |
