[development] Fun CCK idea.

David Metzler metzlerd at metzlerd.com
Sun Jun 3 23:44:34 UTC 2007

And speaking of itches, I've always been a little bothered by the  
fact that flexinode and CKK store there data in generic tables. .

I've been thinking that you could combine the data API project with  
these and use a "convention" based approach where all of these nodes  
were stored in regular tables, one per node type, more like the old  
way contribs used to extend nodes.

In this approach, adding fields would execute DDL not DML for the  
storage mechanism.  I realize that this is a radical approach, but it  
opens the door to more scalability.  (e.g. You could add indexes for  
a content type to make views go faster if they were queried  
frequently.   And it means that you're data can be altered via  
programattically via normal SQL.

The field definition tables would still be the same.

So my question is, has this been considered?  Anyone know where I  
might find the pro/con discussion.  I'd love to contribute to such a  
project if it were likely to be considered favorably.

On Jun 1, 2007, at 4:21 AM, Bèr Kessels wrote:

> Op donderdag 31 mei 2007, schreef Wim Leers:
>> flexinode 2?
>> ***the superceder of CCK***?
>> Is there some place I can read up on this? I wasn't aware of this at
>> all!
> Its nothing official. And nothing big either.
> In short: Don't get nervous. CCK will prolly keep existing. This is  
> just a
> personal itch. My idea:
> * Flexinode has a crappy database model.
> * CCK has a crappy code/hook model, lacks many features, has many
> dirty-hacked-on additions etc.
> Both have bad sides. I consider both to be in such a bad state righ  
> now, that
> I no longer use any of them. And  advice my clients not to use them  
> either.
> I want to move flexinode along, so that this time both the DBA / 
> and/ the
> code /and/ the usability /and/ the interface is done right. If my  
> ideas are
> right, and If I get this off the ground, and if if if if, then  
> either an
> upgrade path for CCK to this thing will come, or else CCK will  
> simply keep
> existing.
> And I have been on this for a long while. Doing the coding and  
> architecturing
> in my few free hours. some notes and ideas on my blog:
> http://webschuur.com/projects/flexinode
> Bèr
> -- 
> Drupal, Ruby on Rails and Joomla! development: webschuur.com |  
> Drupal hosting:
> www.sympal.nl

More information about the development mailing list