sicapitan wrote:
> just seemed a bit excessive to have 1,000,000 files for 1,000,000 tables
Have you ever been to an airport in the US, and seen that big glass
container that shows all the things you're not allowed to bring on an
airplane? Well, at the John Wayne Airport in Orange County,
Califo
ill read that cheers :)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED
Hmm,
And in terms of normal development, whereby having 100 tables would be
considered large..? I think that if you really, really, really wanted
to, you could probably put all of your model class defentions into one
file; but there´s no escaping that there needs to be a model
defenition for each
just seemed a bit excessive to have 1,000,000 files for 1,000,000 tables
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscrib
Hi Sicapitan
What case/problem are you considering...?
You need a model file to define each of your models (Person.php,
Address.php, Order.php, OrderLine.php) so that Cake knows which models
exist. How else would cake know ...? Appart from looking for which
models are defined - to know their gen
well, some databases are huge, trying to display the files in a file
tree, then finding the file, would take forever
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send emai
Uh, yes, that's how it goes. Why, do you think that's too much work?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe f
Normally Model<->Table is a 1:1 relationship. You can easily work
around this, but I think that's against the idea behind Models.
So yes, you should create a [model].php for every table you want to
work with (besides join tables).
--
http://www.thinkingphp.org
http://ww
According the the manual, it says the model relates directly to a
database table. But I have multiple tables. Does this mean I need a
model.php file for each table? Surely not.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Go
