Comments on: PHP ActiveRecord Available for Beta Testing

By: Kien La

Kien La — Sat, 27 Feb 2010 15:59:21 +0000

That’s good to hear. You’re welcome to submit patches by forking the project on github or just emailing us.

By: Peter

Peter — Fri, 26 Feb 2010 17:24:57 +0000

Thank you for publishing these tools! This project has been a huge help to our development efforts. We’ve been doing seo website design and development at industryforge.com for a long time, and love the efficiencies we gain from using your tools. We now have this code running in multiple production environments. We would love to contribute if desired.

By: Kien La

Kien La — Fri, 12 Feb 2010 03:49:37 +0000

Hey Kirk, if you could provide more specifics on the headaches you mentioned I can see if I can address them since more than likely other people have run across the same things and I’d like to get it fixed. Just drop me an email.

We would definitely like for people to contribute. Just fork the project on github or you can email patches to me.

By: Kirk Bushell

Kirk Bushell — Fri, 12 Feb 2010 03:31:59 +0000

First and foremost – great work guys. I’ve been using this in a production environment (with a few headaches), but there’s a few things I thought I might offer in terms of what I think the library should/shouldn’t have.

I think you’ve made a blooper with the design decision to force standards in PHP. With a library like Rails, it’s easy to do because developers are either starting new projects with it, or are working on projects that already use it. I’ve had quite a few problems trying to get the library working with one of our legacy systems. I got there – but not without some changes. First and foremost is PHPActiveRecord’s use of converting field names – this is a problem as all our field names have a capslocked suffix (don’t ask).

Secondly, this was also a problem when reporting errors – as the library tried to humanize the field names, so where we had fields like price_ADV, in the error – it would show up as “price a d v”, as it stuck to it’s own naming conventions.

I’m sure for most cases, the library isn’t going to be an issue, but I think considering that it’s a new library, and a lot of people are going to want to drop it in as a solution to easy database connectivity, forcing standards may not work out as you had hoped.

Keep up the good work

PS – is there any way for us to contribute directly?

By: Björn Göransson

Björn Göransson — Thu, 11 Feb 2010 09:20:39 +0000

Hi,

I’m coming from CodeIgniter Active Record DB library, where one has the ability to specify a TABLE PREFIX (eg “myapp_”) that will be prepended on all table names.

Is this feature available already (I haven’t found it yet, though)

Thanks for a versatile tool.

By: Kirk Bushell

Kirk Bushell — Sun, 03 Jan 2010 23:11:05 +0000

This implementation of ActiveRecord requires PHP 5.3 and above. Namespaces are only available since that release, amongst other things, like anonymous functions.

By: Peter

Peter — Tue, 01 Dec 2009 18:49:39 +0000

Sorry about the previous posts–I just found the answer: PHP 5.3 added namespaces (http://us.php.net/manual/en/language.namespaces.rationale.php) and uses the backslash character as the namespace separator. You must have PHP 5.3 (I should have read more carefully) to use PHP ActiveRecord.

By: Peter

Peter — Tue, 01 Dec 2009 18:41:50 +0000

Somehow, the line of code in question were removed when I posted previously. Here’s the line throwing the error:

ActiveRecord\Config::initialize(function($cfg)

By: Peter

Peter — Tue, 01 Dec 2009 18:38:10 +0000

Any idea why the ActiveRecord\Config is causing problems for me? I thought it might have something to do with magic_quotes, but I turned them off in production env with no luck. Everything works fine on my local system (php 5.3.0), but when I upload to the GoDaddy hosting env (php 5.2.8) I get an error. Here’s the error I get:

Parse error: syntax error, unexpected T_STRING in /my_php_script.php on line 3

And here’s the code:

set_model_directory(’classes’);
$cfg->set_connections(array(’development’ => ‘mysql://’.DB_USER.’:’.DB_PASS.’@’.DB_HOST.’/’.DB_NAME));
});
?>

By: Andrew

Andrew — Thu, 19 Nov 2009 13:53:04 +0000

I mean caching column meta on server using apc memory functions: apc_store and apc_fetch. That’s what I’m doing in my “Active RecordLite” slimmed down version of your Active Record.

By: Andrew

Andrew — Wed, 18 Nov 2009 14:11:31 +0000

what about caching the column meta data from “SHOW COLUMNS FROM ” ?

By: Jacques Fuentes

Jacques Fuentes — Tue, 13 Oct 2009 18:59:09 +0000

Just wanted to let you know, yes, the field information for each table is cached in the Table class.

By: Sathya

Sathya — Tue, 13 Oct 2009 18:42:24 +0000

The whole point of php-activerecord is that you don’t NEED to generate models. You write one simple file with a class extending ActiveRecord\Model and the name of the class automatically inflects from say “Book” to the table name “books”. (And you can explicitly set the table name if you don’t like inflection.) Also, I assume it automatically pulls the describe table information (cacheable?) so you don’t need any configuration file with columns or anything.

Just like Rails’ ActiveRecord::Base

BTW guys behind php-activerecord, I think you’re doing a really good thing here. I absolutely hate Zend_Db, and I hope to one day replace it with your model

By: Kien La

Kien La — Tue, 28 Jul 2009 17:24:00 +0000

You’d have to use the conditions option:

Foo::all(array(’conditions’ => array(”field_a=? and (field_b=? or field_c=?)”, ‘abc’, 0, 1)));

or a slightly simpler form if you don’t have a need to bind any parameters:

Foo::all(”field_a=’abc’ and (field_b=0 or field_c=1)”);

Hope that helps.

By: Urkman

Urkman — Tue, 28 Jul 2009 14:47:58 +0000

Hello,

I took a look at your examples, but I can’t find something like this.
How do you solve a sql query like this:

select *
from table_foo
where field_a = ‘abc’
and ( field_b = 0
or field_c = 1 );

Thanks and greetings,
Urkman