<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/php-orm/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/php-orm/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Sat, 28 Jun 2008 17:21:08 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/php-orm/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>findAll should handle other operators</title><link>https://sourceforge.net/p/php-orm/feature-requests/7/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The findAll method should accept parameters which indicate other operators besides equality (and LIKE). For example, instead of just passing in 'field1'=&amp;gt;'value1', one could also pass in 'field1'=&amp;gt;array('operator'=&amp;gt;'!=', 'value'=&amp;gt;'value1')&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jordan Kasper</dc:creator><pubDate>Sat, 28 Jun 2008 17:21:08 -0000</pubDate><guid>https://sourceforge.net101fe4b2ac439c79bbf0b8252e1b056dbdb4d426</guid></item><item><title>Better DB field attribute definitions</title><link>https://sourceforge.net/p/php-orm/feature-requests/6/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;It would be better if the attributes of a database field/property could be specified in annotation style comment on the field versus in static fields that can't be used with an instance of the class.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jordan Kasper</dc:creator><pubDate>Mon, 16 Jun 2008 16:00:46 -0000</pubDate><guid>https://sourceforge.netcd8d160f627de176974ae07c7002cb202ba6bd89</guid></item><item><title>Documentation &amp; example code</title><link>https://sourceforge.net/p/php-orm/feature-requests/5/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;We would like to have full documentation and example code&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jordan Kasper</dc:creator><pubDate>Fri, 13 Jun 2008 14:13:01 -0000</pubDate><guid>https://sourceforge.nete096f136fa9c8e11074aa45d3aa6291ebd178380</guid></item><item><title>Lazy loading of entity relationships</title><link>https://sourceforge.net/p/php-orm/feature-requests/4/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;*** This request depends on request 1993017 ***&lt;/p&gt;
&lt;p&gt;Allow entity to specify whether its relationships should be loaded immediately upon retrieval or only when requested.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jordan Kasper</dc:creator><pubDate>Fri, 13 Jun 2008 14:11:14 -0000</pubDate><guid>https://sourceforge.netf2aa3338f3e2207043f07f7b75db536810eeda21</guid></item><item><title>Implement entity relationships</title><link>https://sourceforge.net/p/php-orm/feature-requests/3/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Currently the DBEntity class only handles flat fields. We would like to implement support for entity relationships. This would also involve the retrievel of those relationships and the parsing of the Entity which would contain those definitions.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jordan Kasper</dc:creator><pubDate>Fri, 13 Jun 2008 14:04:13 -0000</pubDate><guid>https://sourceforge.net0bace58f5e859cb591b1adcd937228165c7015a4</guid></item><item><title>Abstract Logger module</title><link>https://sourceforge.net/p/php-orm/feature-requests/2/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Currently DBEntity will always use the homegrown Logger object for all logged events. We should abstract out the Logger module so that any logger could be used which follows some specific format. This involves changing DBEntity to accept a Logger object somehow.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jordan Kasper</dc:creator><pubDate>Fri, 13 Jun 2008 14:01:22 -0000</pubDate><guid>https://sourceforge.nete99eac74523fec1cdb7a0c1e91907d6e9ef6e69f</guid></item><item><title>Abstract DB connection module</title><link>https://sourceforge.net/p/php-orm/feature-requests/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Currently DBEntity will always use the homegrown DBConn object for connection to MySQL. We should abstract out the connection module so that any connection module could be used which follows some specific format.&lt;/p&gt;
&lt;p&gt;This may involve multiple tasks:&lt;br /&gt;
- Create abstract DBConn class&lt;br /&gt;
- Implement DBConn with MySQL specific class (and any others)&lt;br /&gt;
- Change DBEntity to accept a DBConn object somehow&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jordan Kasper</dc:creator><pubDate>Fri, 13 Jun 2008 13:55:39 -0000</pubDate><guid>https://sourceforge.net423a71719045d5869b009ad606c7a64189523c2c</guid></item></channel></rss>