Re: a description about some cakephp improvement points

Further points:
1. They forgot that PHP4 is also OK ;)

5. "The framework is inadequate to create new records in
tables that have only one autoincrement (or serial) field"

I read this as being either about a table with a single field (just
the id), or more likely about Cake not liking composite primary keys?
I.E. "Cake is inadequate in that it only supports a single
autoincrement (or serial) field"... but then English is not my first
language either. :)

6.
Cake supports 3rd party software primarily by the vendors folder where
any php library can be placed. Commonly one would then go about
creating a suitable "wrapper" (Component, Helper...) for that library
to have it integrate nicely. These kinds of wrappers are abundantly
available for common libraries like special email libraries and view-
template libraries, like Smarty.

Smart, as an example, can be integrated by using "SmartyView".
http://bakery.cakephp.org/articles/view/smarty-view-for-1-2

And a number of other articles and scripts are apparently available on
the bakery:
http://bakery.cakephp.org/articles/search/tags/smarty

Google finds many more. As for Smarty, my personal view is that it is
a great advantage that Cakes does not require any special templating
system.

/Martin

On Feb 26, 5:48 am, mscdex <msc...@gmail.com> wrote:
> On Feb 25, 10:10 pm, Marcelo Andrade <mfandr...@gmail.com> wrote:
>
> > "The framework is inadequate to create new records in
> > tables that have only one autoincrement (or serial) field"
>
> If I'm understanding this correctly, this is perfectly fine as far as
> CakePHP is concerned. In fact, most new database tables (and many
> CakePHP tutorials out there) created to take advantage of CakePHP's DB
> automagicness almost always use an autoincrementing field for the
> primary key. So that is not an issue at all.
>
> > "The framework requires a database that follows a predefined
> > convention.  So it's impracticable to use it with existing
> > databases from legacy systems.
>
> This isn't true. CakePHP can use pre-existing tables just fine. For
> example, one can simply specify the table name to use in the model
> class: var $useTable = 'PreExistingTableName';
> You can also define many other model attributes to allow CakePHP to
> work with pre-existing databases. Many of these attributes are listed
> in the CakePHP manual:http://book.cakephp.org/view/71/Model-Attributes
> Also, model associations are flexible in that you can do things like
> specify custom queries when finding, deleting, and inserting records
> if you need to.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to cake-php+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---