[Deprecated] DMZ 1.6.2 (DataMapper OverZealous Edition)

[eluser]OverZealous[/eluser]
To All: (Regarding the HTML Form extension)

I understand that the HTML form extension is very useful to many people. However, I do not have the time to maintain it or support it.

I would like to find someone who is willing to take over maintenance and support for this extension. It needs some work, and I just barely have enough time to keep up with the work on the core DMZ library.

If you are interested in maintaining it, please let me know (either through a PM or right here). Just to be clear, everything I have for this extension is already included in the full DMZ download (including the documentation), so if you are interested, feel free to look at the source directly.

I would be willing to include someone else's work with the full download, or pull the HTML extension out of the core download, and link to it somewhere else. The latter is probably preferable, since I won't necessarily upgrade DMZ on the same schedule as the HTML form extension.

[eluser]The Hamburgler[/eluser]
Datamapper has made my job a breeze recently so I guess its time I gave something back!

I've been working on my own CodeIgniter Table and Form libraries: GoodForm and BadTable, for a while now since most of my work is based around CMS web apps.

Both libraries have been designed to work standalone but I have also included DMZ extension files to add their functionality to DM Models.

If any one is interested please download a copy from my site and have a play... There will be bugs, but as i'm currently developing with both systems I should be able to provide fixes pretty quickly.

PM me if you have any questions.

Jim

[eluser]Unknown[/eluser]
Hi I want to thank you for the library, I just started with codeigniter and keep getting an error in the datamapper.


I get the following error when calling delete of the datamapper.

Code:

Fatal error: Class 'post' not found in C:\Users\Samos\xampp\htdocs\productReview\system\application\libraries\datamapper.php on line 1292

The strange thing is that it deletes the record out of the database, but produces this error.

Code:

function delete($object = '', $related_field = '')
    {
        if (empty($object) && ! is_array($object))
        {
            if ( ! empty($this->id))
            {
                // Begin auto transaction
                $this->_auto_trans_begin();

                // Delete this object
                $this->db->where('id', $this->id);
                $this->db->delete($this->table);

                // Delete all "has many" and "has one" relations for this object
                foreach (array('has_many', 'has_one') as $type) {
                    foreach ($this->{$type} as $model => $properties)
                    {
                        // Prepare model
                        $class = $properties['class'];
                        $object = new $class();

$object = new $class(); That is the line where it gives the error.


This is the code how i call the delete:

Code:

if($this->input->post('subDelete'))
            {
                //$id = $this->input->post('id');
                $category->id = 1;
                $category->get()->delete();
            }

Probably it is my fault as i am new to codeigniter, but was hoping to get support maybe here as this is the datamapper thread.

[eluser]OverZealous[/eluser]
3rd-Party Extensions

I've been meaning to figure out how to handle 3rd-Party Extensions. I don't really want to set something up on my own server, since that would be yet another account for everyone to manage.

Instead, I'm thinking of using the existing CodeIgniter Wiki with a special category.

The idea is to have everyone write a Wiki page for their extension, and then make sure it is included in the DMZ Extensions category.

Then I will link to the that page from the DMZ Manual. I figure using a category is best, because then the extensions are listed alphabetically, and it reduces the temptation to resort other people's extensions. ;-)

I've already added links to the 4 included extensions I still support. I might have found someone to take over the HTML Form extension, but still let me know if you are interested.

[eluser]Unknown[/eluser]
Is it possible to use DMZ with multiple database connections? If so, how? I can't seem to locate anything in the documentation about that. Thank you for your patience and your reply.

[eluser]OverZealous[/eluser]
@lexxxluthor

See the $db_params property. It is not officially supported, but feel free to try it out.

If you didn't know, you can search the manual. Searching for "multiple database" leads to the first post of this forum, where it explicitly says:

4. While not tested, it should be easier that ever to work with multiple databases simultaneously. (You won't be able to query across them, but no more hacking to get a different DB for different objects!) See db_params on this page.

[eluser]lsemel[/eluser]
Suggestion for DMZ:

I have been using DMZ Datamapper on large results sets (100,000s of rows) and it quickly runs out of memory because CI loads results sets in full. As a workaround, I've been using this pattern:

Code:

$model = new Model_Object();
# A query returning a big result set.  Instead of calling get(), call get_sql()
$sql = $model->..where clauses,etc....->get_sql();
$results = $this->db->query($sql);
if ($results->num_rows() > 0) {
   # Iterate through the rows without loading the full result set
   while($row = $results->_fetch_object()) {
      # Do something with the row
   }
}

It might be useful for anyone dealing with large result sets if this pattern were part of the library. In place of get, you could call something like get_cursor() and then to read rows you could call something like fetch() which will return a model object populated with the next row. If you did not generate your query with get_cursor(), then fetch() would throw an error.

[eluser]Muser[/eluser]
Thanyou Isemel,

We have to deal with a big result quite soon in a project (I wish) and your suggestion might be very useful

[eluser]lsemel[/eluser]
It might work as a plugin, save for the fact we'd probably want all the get_* methods to work properly.

[eluser]OverZealous[/eluser]
@Isemel, Muser

You may want to have a look at TheJim's solution to this problem. That, and the following post or two, show a way to magically loop over a result set while creating only one object in memory.

It's a slick idea, and doesn't mix standard result set processing with DMZ-style processing. Of course, if you only need the results of the query, that's fine too!