Hello,
I am having some issues setting up the database for my base CMS to use
for all clients. My thoughts were to have the following:
blocks table - this is simply the html, title, description etc for
each page (i.e. home, about us)
menus table - simply contains the menu name (i.e. top navigatio
A very cool, didnt even think about doing it that way, had even
started to look at mysql triggers to do it.
Thankyou robustsolution!
Tony
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post
you dont need to create a controller class for the settings table
just create a model for the settings table
In case user is not created with its settings (in the same add form),
do the following
in the User model put this
function afterSave($created) {
if($created)
{
$this->Setting->create();
Hi Guys,
I am creating an application that hold user names / passwords and
settings.
So I have 2 tables in a DB, users and settings
They have a hasOne relationship.
I have come up to a little problem, When a new user is created i want
to have a row in the settings table created too. is this po
Doesn't anyone have anything to add? I dont' know the best way of
doing this so any help would be great!
Kev
On 5 Oct, 11:18, KevinM2k wrote:
> Hi,
>
> I am creating a custom image gallery, I have categories and sub
> categories, then images within each one.
>
> I am pretty new to cakephp and I
Hi,
I am creating a custom image gallery, I have categories and sub
categories, then images within each one.
I am pretty new to cakephp and I am trying to find out how is the best
way of dealing with the administration area.
For example lets say I create my new photo album under a category of
H
I thought I read somewhere that every table has to have an 'id' column
in CakePHP. Anyway, I deleted the column and everything seems to be
working fine still. I think I got it already. Thanks.
On Feb 9, 10:40 pm, mscdex wrote:
> Also, this is just a personal design decision but I would remove th
column "member_id" in ShortTermLoan is the id of the applicant.
On Feb 9, 10:27 pm, mscdex wrote:
> On Feb 9, 3:11 am, ramonmar...@gmail.com wrote:
>
>
>
> > Here is what I want it to be:
> > Each member can apply for zero or more short term loan(s)
> > A short term loan must have 1 or up to 3 c
Also, this is just a personal design decision but I would remove the
'id' field on the join table and make both of the other two columns
primary keys. That enforces the rule (at the database level anyway)
that a member/comaker cannot be associated with the same loan multiple
times.
--~--~-
On Feb 9, 3:11 am, ramonmar...@gmail.com wrote:
> Here is what I want it to be:
> Each member can apply for zero or more short term loan(s)
> A short term loan must have 1 or up to 3 comakers
> A comaker must also be a member.
> A member could be a comaker.
> It matters to know which member is the
I'm have a problem on how I should 'design' my database for my current
project.
This is my current design:
http://img264.imageshack.us/img264/4396/coopdbjx7.png
(In the image it shows member_int, but the actual field name is member_id
with a data type of int)
Here is what I want it to be:
E
Hey all -- new here, new to CakePHP, but loving it so far. I need some
design suggestions.
I'm writing an application that involves inviting people to a page.
The invites will go out to registered users of the application
("Friends" of the Invitation Owner) and to non-registered users via
email
Hey guys,
I've been wokring on a internet site for awhile now but i lost
interest in it near february and i want to try and get back into it.
So i'm gonna put it into CakePHP (which i did last time i was on it),
but the problem i am trying to get rid of is this.
I have a left and right side, the
13 matches
Mail list logo
