Comments on: Documentation

By: Matt Borja

Matt Borja — Thu, 15 Sep 2011 16:37:33 +0000

Update (replace previous comment):

If you don’t explicitly check the types while making comparisons, you’ll find that

int(0) == (string)’all’ OR (string)’first’

This is why passing 0 doesn’t work or will yield ALL results. Find these lines in ActiveRecord.php (around 362-367) and add the === comparison operator (!== for bool NOT):

if (is_array($id))
$where = “{$item->primary_key} IN (” . implode(“,”, $id) . “)”;
elseif ($id === ‘first’)
$limit = ’1′;
elseif ($id !== ‘all’)
$where = “{$item->table_name}.{$item->primary_key} = $id”;

By: Matt Borja

Matt Borja — Thu, 15 Sep 2011 16:24:25 +0000

Also, I had to add/modify these lines to pass 0 as a parameter of User::find((int)$id) in the event none was specified.

After $select = ‘*’ on Line 361 of ActiveRecord.php
if(is_numeric($id))
$where = “{$item->table_name}.{$item->primary_key} = $id”;
elseif (is_array($id))
$where = “{$item->primary_key} IN (” . implode(“,”, $id) . “)”;

By: Matt Borja

Matt Borja — Thu, 15 Sep 2011 16:09:49 +0000

It appears that if you set more than one PRIMARY KEY, that Users::find($id) will look at the last PRIMARY KEY and I found the $where query in ActiveRecord::generate_find_query() to come out as follows:

WHERE: users.email = ’5′

In my table, I have these fields set as PRIMARY KEYS in the following order:

id
username
email

Just wanted to give you a heads up. For my uses, I’m going to [and might suggest] revising it to look at the first PRIMARY KEY which in most applications is going to be the AUTO_INCREMENT id field.

At any rate, this is why I was having this problem earlier; multiple PRIMARY KEYS.

By: Matt Borja

Matt Borja — Thu, 15 Sep 2011 16:01:07 +0000

Is there a reason why this is throwing the following:

Couldn’t find anything.

Code:
public function view($id = NULL) {
try {
$u = User::find(1);
} catch (Exception $e) {
echo $e->getMessage();
}

if (isset($u))
echo ‘Found ‘ . $u->username;
}

By: Elia

Elia — Fri, 21 Jan 2011 08:37:21 +0000

Thanks for providing this excellent lib! Is there an easy way to debug the SQL generated?

By: Luke

Luke — Thu, 13 Jan 2011 00:53:45 +0000

Shawn, I can’t think of a great way to do that. You could do something like query the Tracks that are released and then get the albums associated with those tracks. If you require that the album have to verify that ALL of its tracks are ‘released’, then you’d probably have to do that in your PHP. Something like:

$tracks = Track::find(‘all’, array(‘conditions’ => “status = ‘released’”, ‘include’ => ‘album’));

next you’d have to loop through the tracks, grab all unique albums and verify that all their tracks have a status of ‘released’. If that hurts performance-wise, you may have to do a manual SQL query.

By: Shawn McCool

Shawn McCool — Wed, 12 Jan 2011 20:39:59 +0000

If, for example, each record in the data model ‘albums’ connects to a number of records in the ‘tracks’ table. Is there a way to pull back albums such that it has only tracks marked as ‘released’?

Currently:

$album = Album::Find(1);
print_r($album->tracks); // lists ALL items

I only want to list items with a condition.

By: Shawn McCool

Shawn McCool — Sun, 09 Jan 2011 20:24:44 +0000

You can create a hook before_create() and before_save() to update the fields “created_at” and “updated_at”.

By: Shawn McCool

Shawn McCool — Sat, 11 Dec 2010 02:30:59 +0000

Does this support any kind of automatic timestamp such as created_at or updated_at?

By: Kalle

Kalle — Thu, 14 Oct 2010 11:14:09 +0000

Hi again..!

I just echo:ed the SQL generated by…
Movie::find(‘all’, array(’select’ => ‘*, sum(movieratings.rating) as sum_rating’, ‘group’ => ‘movie.id’, ‘include’ => ‘movieratings’));

If I use the options “include” AND “select” I can write whatever I want in the “select” option. It doesn’t matter because the generated SQL will contain ALL column names.

Movie::find(‘all’, array(’select’ => ‘movies.id, movies.title’));
…gives me a query for just the specified columns. BUT…!

Movie::find(‘all’, array(’select’ => ‘movies.id, movies.title’, ‘include’ => ‘movieratings’));
…creates a select including ALL columns in both the movies table and the movieratings table.

This must be a bug… Or am I just using the framework wrong?

Anyone?

Help?

Thanks!

{Kalle}