relationships

I'm managing my admin backend with Typus I want to add a field with a checkbox for each category. I used this code: Post: fields: default: name, description, user, categories list: name, description, user, categories form: name, description, user, categories relationships: categories But the result is a textfield with a [] inside: how do I solve this? Is there a native way or must I override the field template? To show the the checkbox for the fields you can use the existing template of the Typus Post: fields: default: name, description, user, categories list: name, description, user,

Basically I have following models in CakePHP: User(id, username) Photo(id, user_id, path) I have set up following relation: User hasMany Photo. On one screen, I would like to list users, and show random photo next to each user. I tried setting up following relation: User hasOne SamplePhoto (where SamplePhoto is just Photo model) but when user has two photos for instance, he is listed twice on the list. basically my question is: can you reduce hasMany relation to hasOne, without adding any fields to table schema presented above? I would like to tell cake - find the first record in the Photo

I was wondering if there are any advantages or disadvantages in storing data into relationships or nodes. For example, if I were to store comments related to a discussion into the DB, should I store the comment data in a "comment" relationship or a "comment" node that is related to the discussion through a separate relationship. The correct data model depends on the types of queries you need to make. You should figure out what your queries are, and then determine a data model that meets these criteria: It allows you to answer all your queries, It allows your queries to finish sufficiently

I am dealing with the following situation: I have two models, an Employee with id and name fields and a Telephone with id , employee_id and flag fields. There is also an one-to-many relationship between these two models, that is an employee may have many telephones and a telephone may belong to a single employee. class Employee extends Model { public function telephones() { return $this->hasMany(Telephone::class); } } class Telephone extends Model { public function employee() { return $this->belongsTo(Employee::class); } } The Employee model references a table employees that exists in database

I have three tables: users , ideas , and ideas_likes . The ideas_likes table looks like: ideas_likes ------------ id primary key user_id foreign key idea_id foreign key liked boolean There's already a one-to-many relationship set up between users and ideas. It looks something like this: class User extends Ardent implements UserInterface, RemindableInterface { use UserTrait, RemindableTrait; protected $table = 'users'; public function ideas() { return $this->hasMany('Idea'); } } Similarly, the idea model looks like this: class Idea extends Ardent { protected $table = 'ideas'; public function