Hi, I have a persistent object mapped to a table with a DateTime field, but I can\'t get it to store the current datetime. I have tried setting the object property to \'Now()\' and the actual value \'2006-12-04 11:09:15\' etc. but neither way worked. Can anyone tell me how to achieve this? Thanks, Dan
Hi, I have an "Event" object and a "Person" object. The event object has the fields "created_by" and "lastmod_by", which are integers, and the person object has an id field. I want to map two independent relations between these objects, and fetch the related person object for the event field created_by or the event field lastmod_by independently of each other. Can this be done? How? Best regards, Tobias
Hi Dan! On 12/04/2006 02:44 AM dan.humphrey@... wrote: > I have a persistent object mapped to a table with a DateTime field, > but I can\'t get it to store the current datetime. > I have tried setting the object property to \'Now()\' and the actual > value \'2006-12-04 11:09:15\' etc. but neither way worked. > Can anyone tell me how to achieve this? DateTime columns are not portable between databases, therefore not supported by most of our database components (AFAIK). I would suggest using an integer field and working with timestamps instead. Regards, Toby -- -- Mit freundlichen Gruessen / Med vennlig hilsen / Best regards Tobias Schlitt (GPG Key: 0xC462BC14) System developer for the eZ components project ts@... | eZ systems | ez.no
Hi Tobias! On 12/05/2006 03:51 PM Tobias Sahlman wrote: > I have an "Event" object and a "Person" object. The event object has the > fields "created_by" and "lastmod_by", which are integers, and the person > object has an id field. I want to map two independent relations between > these objects, and fetch the related person object for the event field > created_by or the event field lastmod_by independently of each other. Can > this be done? How? I'm sorry, this is currently not possible. Please file a feature request for it on http://issues.ez.no, so we can take a look at the issue after 2006.2 release. Thanks! Toby -- -- Mit freundlichen Gruessen / Med vennlig hilsen / Best regards Tobias Schlitt (GPG Key: 0xC462BC14) System developer for the eZ components project ts@... | eZ systems | ez.no
Hi ez-people, I'm Thomas Koch from Essen, Germany, near to Dortmund. I've been on the Weekender and am quite impressed of some of the ez people and their projects. My question: I've been looking on phpDocumentor and doxygen to use it for eGroupware. I favour doxygen, but since ez uses phpDocumentor I thought that I should give it a second try. But when phpDoc runs over the whole eGroupware, it runs out of memory. It also won't help to increase the memory limit since the codebase of eGW is veeeery large. Did you already run in this problem with the components? I've read the discussions on this list about phpDoc vs. doxygen, but unfortunately there isn't a final summary why you decided for phpDoc. I thought, that it's easy to take eZ as a model when having design questions, but this issue makes me insecure. Best, Thomas Koch
Hello Thomas, As you already mention, we had indeed a long discussion about what to use. Some people favored doxygen (including me) and some others phpDocumentor. Looking through my old emails I found the decision why we finally chose for phpDocumentor: --- We just decided to go for PHPDocumentor to generate our documentation. This was an extremely hard decision. However, these undeniable facts made us go for PHPDocumentor: - PHP edit tools have support for PHP syntax, doxygen syntax is not supported. - Doxygen lacks the support for <at> param TYPE description. Even though we have a patch for this it is not certain that we can get this patch into doxygen. - We have some trouble with the output of doxygen which can only be fixed through the usage of XSLT. This is hard maintain and to write. --- If I would start a new project from scratch, I would choose Doxygen, for the following reaons: - Doxygen is quicker and more stable. - [$param TYPE description] is not really needed anymore, because PHP supports Typehinting. I think that Doxygen can read the typehints and put it in the documentation. (Basic types may be missing) - As I remember correctly, fixing the output for PhpDocumentor was also not(Continue reading)
Thanks a lot for clearing it up to me! Thomas Koch Am Donnerstag 07 Dezember 2006 13:46 schrieb Raymond Bosman: > Hello Thomas, > > As you already mention, we had indeed a long discussion about what to use. > Some people favored doxygen (including me) and some others phpDocumentor. > Looking through my old emails I found the decision why we finally chose for > phpDocumentor: > > --- > > We just decided to go for PHPDocumentor to generate our documentation. > This was an extremely hard decision. However, these undeniable facts > made us go for PHPDocumentor: > - PHP edit tools have support for PHP syntax, doxygen syntax is not > supported. > - Doxygen lacks the support for <at> param TYPE description. Even though we > have a patch for this it is not certain that we can get this patch into > doxygen. > - We have some trouble with the output of doxygen which can only be > fixed through the usage of XSLT. This is hard maintain and to write. > > --- > > > If I would start a new project from scratch, I would choose Doxygen, for > the following reaons:(Continue reading)
Hi all! I just noticed, that ezcBaseStruct does not require the ezcBaseStruct class does not require struct classes to implement __set_state() (which is necessary for proper serialization). Since it makes sense for struct classes to be serializeable. We could make the class abstract and force the implementation, but this solution would break BC, since ezcBaseStruct is not marked <at> private. So, what about it? Regards, Toby -- -- Mit freundlichen Gruessen / Med vennlig hilsen / Best regards Tobias Schlitt (GPG Key: 0xC462BC14) System developer for the eZ components project ts@... | eZ systems | ez.no
hi
i have a strange behaviour.
i have an abstract class (named Package_Package) in which i make a
instance from the template ezcTemplate();
in 2 subclasses i do some sql queries and return html from a template
like:
<code>
class Package_News extends Package_Package implements
Package_Packageinterface {
private $title = "News";
private $DB_News;
public function __construct() {
parent::__construct();
$this->DB_News = new DB_News();
}
public function getTitle() {
return $this->title;
}
public function getContent() {
$newsdata = $this->DB_News->getAllNews();
try {
$this->TPL->send->title = $this->title;
(Continue reading)
On Thu, 7 Dec 2006, Tobias Schlitt wrote: > I just noticed, that ezcBaseStruct does not require the ezcBaseStruct > class does not require struct classes to implement __set_state() (which > is necessary for proper serialization). Since it makes sense for struct > classes to be serializeable. > > We could make the class abstract and force the implementation, but this > solution would break BC, since ezcBaseStruct is not marked <at> private. > > So, what about it? I don't think that we should require this, as for many it might not even make sense to serialize. regards, Derick
RSS Feed1 | |
|---|---|
1 | |
7 | |
3 | |
5 | |
6 | |
7 | |
50 | |
15 | |
17 | |
23 | |
9 | |
22 | |
34 | |
17 | |
16 | |
19 | |
35 | |
40 | |
87 | |
77 | |
67 | |
30 | |
35 | |
18 | |
45 | |
8 | |
28 | |
104 | |
123 | |
43 | |
51 | |
58 | |
63 | |
123 | |
48 | |
97 | |
29 | |
45 | |
130 | |
199 | |
143 | |
186 | |
114 | |
39 | |
74 | |
130 | |
59 | |
68 | |
58 | |
83 | |
207 | |
109 | |
77 | |
266 | |
77 | |
46 | |
106 | |
66 | |
220 | |
134 | |
227 | |
87 | |
249 |
