I've been trying to get a two table realtional DB going using the built
in bakery.  Every time I get to baking the view I run into php error:

"Call to a member function on a non-object .... dbo_source.php line
582"


I wanted to clarify that my naming conventions were correct when going
through the baking process.

tables:   psick_cats,  psick_links    (psick_links has a field
psick_cat_id  i.e. belongs to cats)


When building the Model the bakery does a good job of pre-naming
everyhting for me  (model PsickCat and PsickLink ...   At this time I
also add a 1 to many for cats to links and belongs to association for
links)

Next to make controllers::    I'm asked to specificy the controllers
that I want to make.  I use  PsickLinks and PsickCats  (not 100% on
this, but i believe it to be right)

i choose to build interactively.

during this phase I am asked the question,

***Would you like this controller to use other models besides 'xxxxxx'

    This is where i'm confused,  My original interpretation was that
Yes, since i have a key relationship between the tables I want to use
this, but I'm not sure weather this means the one controller would
controll multiple classes?

I've tried a lot of variations, and ultimately

I burn a build and specify controller name "PsickLinks"

when i select build the basic views i get the following eerr:
PHP Fatal error:  Call to a member function on a non-object in ...
dbo_source.php on line 582

PsickCats view builds fine

http://stahler.org/psick.txt  <-- table deffs are here
http://psick.org/psick_cats/  <-- cats built there
http://psick.org/psick_links/  <-- links is missing the views


--~--~---------~--~----~------------~-------~--~----~
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]
For more options, visit this group at http://groups.google.com/group/cake-php
-~----------~----~----~----~------~----~------~--~---

Reply via email to