Categories and Subcategories

The adjacency model

The fundamental structure of the adjacency model is a one-to-many relationship between a parent entry and its child entries. As with any one-to-many relationship, the child entries carry a foreign key to their parent. What makes the adjacency model different is that the parent and child entries are both stored in the same table.

create table categories
( id       integer     not null  primary key 
, name     varchar(37) not null
, parentid integer     null
, foreign key parentid_fk (parentid) 
      references categories (id)
);

Here's some sample data that might populate this table, and we should be able to get an idea of the parent-child relationships (if not grasp the entire hierarchy) just by looking at the data:

id	name	parentid
1	animal	NULL
2	vegetable	NULL
3	mineral	NULL
4	doggie	1
5	kittie	1
6	horsie	1
7	gerbil	1
8	birdie	1
9	carrot	2
10	tomato	2
11	potato	2
12	celery	2
13	rutabaga	2
14	quartz	3
15	feldspar	3
16	silica	3
17	gypsum	3
18	hunting	4
19	companion	4
20	herding	4
21	setter	18
22	pointer	18
23	terrier	18
24	poodle	19
25	chihuahua	19
26	shepherd	20
27	collie	20

Displaying all categories and subcategories: site maps and navigation bars

To display the hierarchy, we must first retrieve it. The following method involves using as many LEFT OUTER JOINs as necessary to cover the depth of the deepest tree. For our sample data, the deepest tree has four levels, so the query requires four self-joins. Each join goes "down" a level from the node above it. The query begins at the root nodes.

select root.name  as root_name
     , down1.name as down1_name
     , down2.name as down2_name
     , down3.name as down3_name
  from categories as root
left outer
  join categories as down1
    on down1.parentid = root.id
left outer
  join categories as down2
    on down2.parentid = down1.id
left outer
  join categories as down3
    on down3.parentid = down2.id
 where root.parentid is null
order 
    by root_name 
     , down1_name 
     , down2_name 
     , down3_name

Notice how the WHERE clause ensures that only paths from the root nodes are followed. This query produces the following result set:

root_name	down1_name	down2_name	down3_name
animal	birdie	NULL	NULL
animal	doggie	companion	chihuahua
animal	doggie	companion	poodle
animal	doggie	herding	collie
animal	doggie	herding	shepherd
animal	doggie	hunting	pointer
animal	doggie	hunting	setter
animal	doggie	hunting	terrier
animal	gerbil	NULL	NULL
animal	horsie	NULL	NULL
animal	kittie	NULL	NULL
mineral	feldspar	NULL	NULL
mineral	gypsum	NULL	NULL
mineral	quartz	NULL	NULL
mineral	silica	NULL	NULL
vegetable	carrot	NULL	NULL
vegetable	celery	NULL	NULL
vegetable	potato	NULL	NULL
vegetable	rutabaga	NULL	NULL
vegetable	tomato	NULL	NULL

Each row in the result set represents a distinct path from a root node to a leaf node. Notice how the LEFT OUTER JOIN, when extended "below" the leaf node in any given path, returns NULL (representing the fact that there was no node below that node, i.e. satisfying that join condition).
As we can see, this result set contains all our original categories and subcategories. If the categories and subcategories are being displayed on a web site, this query can therefore be used to generate the complete site map. An abbreviated query, that goes down only a certain number of levels from the roots, regardless of whether there may be nodes at deeper levels, can be used for the site's navigation bar.
We can display this sample data using nested unordered lists like this:

• animal
  
  • birdie
  • doggie
    
    • companion
      
      • chihuahua
      • poodle
    • herding
      
      • collie
      • shepherd
    • hunting
      
      • pointer
      • setter
      • terrier
  • gerbil
  • horsie
  • kittie
• mineral
  
  • feldspar
  • gypsum
  • quartz
  • silica
• vegetable
  
  • carrot
  • celery
  • potato
  • rutabaga
  • tomato

The path to the root: the breadcrumb trail

Retrieving the path from any given node, whether it is a leaf node or not, to the root at the top of its path, is very similar to the site map query. Again, we use LEFT OUTER JOINs, but this time we go "up" the tree from the node, rather than "down."

select node.name as node_name 
     , up1.name as up1_name 
     , up2.name as up2_name 
     , up3.name as up3_name 
  from categories as node
left outer 
  join categories as up1 
    on up1.id = node.parentid  
left outer 
  join categories as up2
    on up2.id = up1.parentid  
left outer 
  join categories as up3
    on up3.id = up2.parentid
order
    by node_name    

Here's the result set from this query:

node_name	up1_name	up2_name	up3_name
animal	NULL	NULL	NULL
birdie	animal	NULL	NULL
carrot	vegetable	NULL	NULL
celery	vegetable	NULL	NULL
chihuahua	companion	doggie	animal
collie	herding	doggie	animal
companion	doggie	animal	NULL
doggie	animal	NULL	NULL
feldspar	mineral	NULL	NULL
gerbil	animal	NULL	NULL
gypsum	mineral	NULL	NULL
herding	doggie	animal	NULL
horsie	animal	NULL	NULL
hunting	doggie	animal	NULL
kittie	animal	NULL	NULL
mineral	NULL	NULL	NULL
pointer	hunting	doggie	animal
poodle	companion	doggie	animal
potato	vegetable	NULL	NULL
quartz	mineral	NULL	NULL
rutabaga	vegetable	NULL	NULL
setter	hunting	doggie	animal
shepherd	herding	doggie	animal
silica	mineral	NULL	NULL
terrier	hunting	doggie	animal
tomato	vegetable	NULL	NULL
vegetable	NULL	NULL	NULL

Here each row in the result set is a single path, one for every node in the table. On a web site, such a path is often called a breadcrumb trail. (This name is somewhat misleading, because it suggests that it might represent how the visitor arrived at the page, which is not always the case. The accepted meaning of breadcrumb is simply the path from the root.)
In practice, we'd have a WHERE clause that would specify a single node, so in effect, the results above are all of the breadcrumbs in the table.
To display a breadcrumb trail in the normal fashion, from root to node, just display the result set columns in reverse order, and ignore the nulls. For example, let's say we run the above query for the category "companion" and get this:

node_name	up1_name	up2_name	up3_name
companion	doggie	animal	NULL

The breadcrumb would look like this:

animal » doggie » companion

Simple, eh?

Resources

Listamatic: one list, many options

The power of CSS when applied to the lowly UL.

Trees in SQL by Joe Celko

The nested set model, alternative to the adjacency list model.

Storing Hierarchical Data in a Database

Modified Preorder Tree Traversal method.

Relational Integrity

Primary and foreign keys and stuff like that.

"Fatal error: Class 'Debugger' not found" in paging cakephp

Fatal error: Class 'Debugger' not found in D:\Webserver\Apache2\htdocs\Bitbucket\mdkn\lib\Cake\View\Helper\JsHelper.php on line 422

Fix Error:

Change the level error of your core.php in your app from 'level' => E_ALL & ~E_DEPRECATED, to 'level' => E_ALL & ~E_DEPRECATED & ~E_STRICT,

Best PHP Frameworks for 2014

The end of the year is upon us. Lots has changed in the PHP world in the past 365 days, and the PHP framework scene is more densely populated than ever. Everyone and their dog seems to have an idea of what a good framework should look like, but in the end, do we even know which frameworks actually end up being used in production projects? How many go beyond the stage of thousands of people just doing a demo app in them?

In a small survey we've held open for the past week or so (which has also been mentioned in PHP Weekly), we asked these questions to decide which frameworks deserve our attention in 2014 the most. The prerequisite for participation was merely having experience in more than one framework, seeing as it's pointless to ask someone what their favorite bar was if they've only drunk in one place.

Unfortunately, a big percentage of the answers had to be discarded due to people either refusing the notion that WordPress and similar suites aren't frameworks, or simply due to a blatant disregard of instructions – many responses were written by people who only ever worked in one framework. While their enthusiasm for this framework of choice is noteworthy and admirable, the final result which may end up being skewed by such approaches could hardly be called objective.

Results summary

After discarding the invalid responses, and manually verifying every participant, we were left with the following data:

 

According to the results, the most promising frameworks for 2014 seem to be:

• Laravel
• Phalcon
• Symfony2

 Reference link: http://www.sitepoint.com/best-php-frameworks-2014/

How to Add and Upload an Image using CKEditor

Enable the file upload dialogue box

Download package ckeditor standard here

Find the directory in your web site where you've saved and extracted CKEditor, and then it's a couple more directories further down we need to go:
ckeditor\plugins\image\dialogs
Inside that folder is a file called image.js - open this up. If you haven't already got it, I'd recommend the brilliant Notepad++ to use rather than the basic Notepad programme which comes free with Windows.

You can see more to here http://www.paulfp.net/blog/2010/10/how-to-add-and-upload-an-image-using-ckeditor/