On Jan 13, 2008 9:45 PM, jm <[EMAIL PROTECTED]> wrote:
>
> Yariv Sadan wrote:
> > On Jan 13, 2008 2:49 PM, jm <[EMAIL PROTECTED]> wrote:
>
> >> Second, is there anyway to use the standard MVC setup for one component
> >> with out a table in the database? As erlyweb automatically tries to
> >> inspect the tabe it generates this error,
> >>
> >> ** exited: {no_such_table,{{module,modulename},{table,modulename}}} **
> >
> > You can do this by removing the "model" modules (modules that don't
> > end with "_controller" or "_view") from src/components. ErlyWeb only
> > attempts to inspect database tables for model modules under
> > src/components.
> >
>
> mmm, not optimal as there are a number of methods which naturally fall
> into a model as these are calculations used by other components. These
> are methods that shouldn't be publicly available through the controller,
> but there are other methods which are on should be available in the
> controller so private() -> true won't help me here. Have you thought
> about adding an inheritance parameter like in controller and view to
> control this? Exactly what and how I'm trying is still a little up in
> the air. I may not be approaching this in the best way possible.

For now, you can keep the models outside of the components subdir and
ErlyDB will ignore them. I do think it would be a nice feature to be
able to export functions from public controllers but tell ErlyWeb to
hide those functions from requesting clients.

>
>
> Jeff.
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"erlyweb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to