Evo or Revo?

@TimGS
You didn’t save the chunk back in the database.
Now you need more lines to update the chunk using the DBAPI.

<?php
    $chunk = file_get_contents(MODX_BASE_PATH . 'components/spform/banlist.inc.php');
    $modx->db->insert(array('name'=>'spfbanlist', 'snippet'=>$chunk), $modx->getFullTablename('site_htmlsnippets'));
?>

Quote from: lossendae at Apr 30, 2011, 05:26 AM

@TimGS
You didn’t save the chunk back in the database.
Now you need more lines to update the chunk using the DBAPI.

Ooops - I ’coded’ it the wrong way round i.e. chunk to file.

The right way round (I hope ) in Evo, albeit untested, in two lines (though it could be a one-liner):

<?php
    $chunk = file_get_contents(MODX_BASE_PATH . 'components/spform/banlist.inc.php');
    $modx->db->insert(array('name'=>'spfbanlist', 'snippet'=>$chunk), $modx->getFullTablename('site_htmlsnippets'));
?>

I’m still not seeing how learning xPDO is going to help the coding of my websites.

-- Tim.

<?php
  
    $chunk = file_get_contents(MODX_BASE_PATH . 'components/spform/banlist.inc.php');
    $result = $modx->db->select( '*', $modx->getFullTablename('site_htmlsnippets'), 'name="spfBanlist"');
    if( $modx->db->getRecordCount( $result ) >= 1 ) {
        $modx->db->update(array('snippet'=>$chunk), $modx->getFullTablename('site_htmlsnippets'),'name="spfBanlist"');   
    }    
    else{
        $modx->db->insert(array('name'=>'spfbanlist', 'snippet'=>$chunk), $modx->getFullTablename('site_htmlsnippets'));       
    }
    
    
?>

<?php
    $chunkObj = $modx->getObject('modChunk', array('name'=>'spfBanlist'));
    if (empty($chunkObj)){
       $chunkObj = $modx->newObject('modChunk');
       $chunkObj->set('name','spfBanlist'); 
    }
    $fName = MODX_CORE_PATH . 'components/spform/banlist.inc.php';
    $chunkObj->setContent(file_get_contents($fName));
    $chunkObj->save();
    
?>

this example isn’t complete.

what would you say is easier and more elegant, more intuitiv to code, easier to read once you know how xpdo works:
A:

<?php
  
    $chunk = file_get_contents(MODX_BASE_PATH . 'components/spform/banlist.inc.php');
    $result = $modx->db->select( '*', $modx->getFullTablename('site_htmlsnippets'), 'name="spfBanlist"');
    if( $modx->db->getRecordCount( $result ) >= 1 ) {
        $modx->db->update(array('snippet'=>$chunk), $modx->getFullTablename('site_htmlsnippets'),'name="spfBanlist"');   
    }    
    else{
        $modx->db->insert(array('name'=>'spfbanlist', 'snippet'=>$chunk), $modx->getFullTablename('site_htmlsnippets'));       
    }
    
    
?>

B:

<?php
    $chunkObj = $modx->getObject('modChunk', array('name'=>'spfBanlist'));
    if (empty($chunkObj)){
       $chunkObj = $modx->newObject('modChunk');
       $chunkObj->set('name','spfBanlist'); 
    }
    $fName = MODX_CORE_PATH . 'components/spform/banlist.inc.php';
    $chunkObj->setContent(file_get_contents($fName));
    $chunkObj->save();
    
?>

my favorite is B

Didn’t see this mentioned yet - but the xPDO layer allows database abstraction which makes it able of working on different database systems. 2.1 also supports sqlsrv next to mysql.

Also - the underlying database structure can me modified to be more efficient / make more sense, while keeping a clean upgrade path if you use the recommended object approach.

Probably the biggest reason to learn/use xPDO is because it’s OOP - Object Oriented Programming. You can do it without, but there are some distinct advantages on it that Google can tell you about better than I can.

You and Bob did different things with your code.
Bob is updating an existing record.
You are inserting a new one.

I’m still not seeing how learning xPDO is going to help the coding of my websites.
-- Tim.