I haven’t tested this manually yet. But I am supposed to get a latlong a bit northeast.

I didn’t get enough time to test it with other latlong sets. Will do it.

2) Can you give me the example of this you are working with so I can try to debug the problem.

Or am I missing something completely?

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

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?

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.