Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>there is a solution to fit the coffeemachine problem</p> <pre><code>abstract class Coffee { protected $cup = array(); public function getCup() { return $this-&gt;cup; } } class SimpleCoffee extends Coffee { public function __construct() { $this-&gt;cup['coffeePowder'] = 1; $this-&gt;cup['water'] = 20; $this-&gt;cup['spoon'] = FALSE; } } abstract class Decorator extends Coffee { private $_handler = null; public function __construct($handler) { $this-&gt;_handler = $handler; $this-&gt;cup = $handler-&gt;cup; } } class SugarCoffee extends Decorator { public function __construct($handler) { parent::__construct($handler); $this-&gt;cup['water'] -= 1; $this-&gt;cup['sugar'] = 1; $this-&gt;cup['spoon'] = TRUE; } } class MilkCoffee extends Decorator{ public function __construct($handler) { parent::__construct($handler); $this-&gt;cup['water'] -= 5; $this-&gt;cup['milk'] = 5; } } $wantSugar = TRUE; $wantMilk = TRUE; $coffee = new SimpleCoffee(); if($wantSugar) $coffee = new SugarCoffee($coffee); if($wantMilk) $coffee = new MilkCoffee($coffee); $cupOfCoffee = $coffee-&gt;getCup(); var_dump($cupOfCoffee); </code></pre> <p>and there is another <code>real world example</code>, I hope it can help you:</p> <pre><code>abstract class MessageBoardHandler { public function __construct(){} abstract public function filter($msg); } class MessageBoard extends MessageBoardHandler { public function filter($msg) { return "added in messageBoard|".$msg; } } class MessageBoardDecorator extends MessageBoardHandler { private $_handler = null; public function __construct($handler) { parent::__construct(); $this-&gt;_handler = $handler; } public function filter($msg) { return $this-&gt;_handler-&gt;filter($msg); } } class HtmlFilter extends MessageBoardDecorator { public function __construct($handler) { parent::__construct($handler); } public function filter($msg) { return "added in html filter|".parent::filter($msg); } } class SensitiveFilter extends MessageBoardDecorator { public function __construct($handler) { parent::__construct($handler); } public function filter($msg) { return "added in sensitive filter|".parent::filter($msg); } } $html = TRUE; $sencitive = TRUE; $obj = new MessageBoard(); if($html) { $obj = new SensitiveFilter($obj); } if($sencitive) { $obj = new HtmlFilter($obj); } echo $obj-&gt;filter("message"); </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POfull inheritance behaviour with Decorator in php
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USFu Xu
    1. USFu Xu
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COBecause it breaks the decorator-chaining. It's ok for the first of the chain (the one I called "Foo"), which will be always instanciated, but for the others (Bar, Baz, etc), the chain of inheritance have to be programaticaly defined, according to the context. If you hardcode like that (is it really what you meant?): `class Baz extends Bar{...` it becomes a classical "static" inheritance. Anyway, thank you for answering, if you want to edit or to add a new answer, it will be welcome.
      singulars
      1. PO
      1. USPierre
    2. COI updated the sourcecode. I don't know if it is what you want.
      singulars
      1. PO
      1. USFu Xu
    3. COYes! It's more something like that. But you said that the decorator-chaining is not broken, and it is. The abstraction of behaviour is something I want, but not only. I want that according to the context, the object can be always a component, sometimes a Foo, sometimes a Bar (what you've done) and sometimes a Foo AND a Bar (with Bar "extends" Foo, what you have not done). I enjoy your efforts, continue.
      singulars
      1. PO
      1. USPierre
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload