Jesus M. Castagnetto | 1 May 07:40 2002
Picon

Re: Re: [PEAR] CVS tree: /pear versus /php4/pear and bug report for pear package manager


--- Tal Peer <tal <at> xed.dk> wrote:
> >> Last, but not least, the PHPDOC from phpdoc.de seems to have big
> >> problems during parsing phase because cr or cr/lf. Does this have been
> >> improve recently?
> >
> > Wrong group. Ask in the phpdoc mailing list, in particular as the
> > german editors/translators. Each translation team has its own
> > coordinator and procedures, ask them directly.
> 
> Actually, this is the right place  to ask, since phpdoc != PHPDoc (which is
> part of pear).

My mistake, did not remember that the original phpdoc was from that URL.

> 
> -- 
> "Boredom is our only enemy"
> 
> Tal Peer
> 
> 

=====
--- Jesus M. Castagnetto (jcastagnetto <at> yahoo.com)

Research:
 http://metallo.scripps.edu/
Personal: http://www.castagnetto.org/

(Continue reading)

Tomas V.V.Cox | 1 May 19:21 2002

Re: Contributing / DB_Object

MARTY Fabien wrote:
> 
> (Alan)
> > you may want to look at
> >
> > http://www.akbkhome.com/Projects/db_oo+-+an+object+based+Sql+builder+and+wr
> >apper+for+peardb/usage.html
> > I'm still trying to get more docs up, but this design is more object
> > based, most of the methods take no arguments, and usually no more than
> > two are in the core class..
> > IMO the design you had is not really taking much advantage of
> > class/objects, rather just wrapping functions in classes.. (but I'm no
> > expert :)
> 
> You are right. But in my case, I don't really need to advantages of
> class/object. Maybe, i can add a constructor in order to remove the $db from
> the arguments of methods. But... in the most of uses, it add one line to
> write for user.
> 
> But I'm very surprised by the class db_oo. It seems to be excellent (when i
> look to the examples).

Very nice class indeed. I could share some code to add AND/OR SQL
functionality. My fear with that classes is the support for JOIN/UNIONs,
do that class support them?

> Why is this class not in PEAR CVS ??? Why is this
> class not in PEAR packages ???

Alan is always welcome to suggest the class for being part of PEAR and
(Continue reading)

Stig S. Bakken | 1 May 20:53 2002
Picon

Re: suggestion php4/pear/Console/PHPINI.php

This will be dealt with in sapi/cli as of PHP 4.3.  Most of the defaults 
you suggest below have already been suggested on php-dev.  I guess the 
exception is implicit_flush and output_buffering.  The installer actually 
uses output buffering a few places.

My vote is for not messing with this in user space now, but wait for 4.3.

 - Stig

On 30 Apr 2002, Tomas V.V.Cox wrote:

> Any interest on having this PHPINI.php file for fast adapt any php
> script for running under the console?
> 
> Here are the contents:
> 
> <?php
> error_reporting(E_ALL);
> ini_set('allow_url_fopen', true);
> ini_set('output_buffering', 0);
> ini_set('implicit_flush', true);
> ini_set('max_execution_time', 0);
> ini_set('track_errors', true);
> ini_set('html_errors', false);
> ini_set('warn_plus_overloading', true);
> ini_set('display_startup_errors', true);
> ini_set('display_errors', true);
> ini_set('allow_call_time_pass_reference', false);
> ini_set('short_open_tag', false);
> ?>
(Continue reading)

Jesus M. Castagnetto | 1 May 22:54 2002
Picon

Bug in XML_Tree when parsing XML files

Was testing XML_Tree parsing some files from the PHPDOC directory (the PHP
Documentation in cvs.php.net/cvs.php/phpdoc), and found out a really nasty bug
that makes this class less than useful.

It seems like XML_Tree (or XML_Parser, I had not isolated the problem), just
misses content when parsing the files. I used the following code:

=== testTree.php ===

require_once "XML/Tree.php";

// change to wherever you have checked out phpdoc
$phpdoc = "/home/jesus/devel/php/phpdoc/";
$entities = "entities/global.ent";
$file = "en/language/control-structures.xml";

$xmlarr = file($phpdoc.$file);
$entarr = file($phpdoc.$entities);

$doctype = '<!DOCTYPE chapter PUBLIC "-//Norman Walsh//DTD DocBk XML V3.1.4/EN"
				"http://nwalsh.com/docbook/xml/3.1.4/db3xml.dtd" [
'.implode("",$entarr)."\n]>\n";
$xmltop = $xmlarr[0];
$xmlbody = implode("",array_slice($xmlarr,1));

$xmldoc = $xmltop.$doctype.$xmlbody;
//echo $xmldoc;
$tree = new XML_Tree();
$root = $tree->getTreeFromString($xmldoc);
//$root->dump();
(Continue reading)

jmcastagnetto | 1 May 22:57 2002
Picon
Picon

Bug #16952: Bug when parsing XML file using XML_Tree

From:             jmcastagnetto <at> php.net
Operating system: RH Linux 6.1
PHP version:      4.2.0
PHP Bug Type:     PEAR related
Bug description:  Bug when parsing XML file using XML_Tree

Was testing XML_Tree parsing some files from the PHPDOC directory (the PHP
Documentation in cvs.php.net/cvs.php/phpdoc), and found out a really nasty
bug that makes this class less than useful.

It seems like XML_Tree (or XML_Parser, I had not isolated the problem),
just misses content when parsing the files. I used the following code:

=== testTree.php ===

require_once "XML/Tree.php";

// change to wherever you have checked out phpdoc
$phpdoc = "/home/jesus/devel/php/phpdoc/";
$entities = "entities/global.ent";
$file = "en/language/control-structures.xml";

$xmlarr = file($phpdoc.$file);
$entarr = file($phpdoc.$entities);

$doctype = '<!DOCTYPE chapter PUBLIC "-//Norman Walsh//DTD DocBk XML
V3.1.4/EN"
				"http://nwalsh.com/docbook/xml/3.1.4/db3xml.dtd" [
'.implode("",$entarr)."\n]>\n";
$xmltop = $xmlarr[0];
(Continue reading)

jmcastagnetto | 1 May 23:01 2002
Picon
Picon

Bug #16952 Updated: Bug when parsing XML file using XML_Tree

 ID:               16952
 Updated by:       jmcastagnetto <at> php.net
 Reported By:      jmcastagnetto <at> php.net
 Status:           Open
 Bug Type:         PEAR related
 Operating System: RH Linux 6.1
 PHP Version:      4.2.0
 New Comment:

BTW, I am using the latest version of XML_Tree from the CVS tree
(pear/XML_Tree), and the XML_Parser included w/ PHP 4.2.0

Previous Comments:
------------------------------------------------------------------------

[2002-05-01 16:57:44] jmcastagnetto <at> php.net

Was testing XML_Tree parsing some files from the PHPDOC directory (the
PHP Documentation in cvs.php.net/cvs.php/phpdoc), and found out a
really nasty bug that makes this class less than useful.

It seems like XML_Tree (or XML_Parser, I had not isolated the problem),
just misses content when parsing the files. I used the following
code:

=== testTree.php ===

require_once "XML/Tree.php";

// change to wherever you have checked out phpdoc
(Continue reading)

Alan Knowles | 2 May 01:26 2002

RFI: DB_OO? Was [PEAR-DEV] Contributing / DB_Object

>
>
Comments Inline:

>>
>>
>>But I'm very surprised by the class db_oo. It seems to be excellent (when i
>>look to the examples).
>>
>
>Very nice class indeed. I could share some code to add AND/OR SQL
>
(see TODO)

>
>functionality. My fear with that classes is the support for JOIN/UNIONs,
>do that class support them?
>

I did start looking at this - its under the db_oo_crosstable, however It 
got to the point where the simplicity of using this type of data 
modelling was kind of lost when you start working with JOINS/UNIONS - it 
was just easier to go back to hard coded SQL for a join query...., 
(which can be supported - see db_oo::query in additional methods

even alot of the 'additional features for queries' could be described as 
an overkill, however it's always a fine balance (if you are building a 
query from mutiple conditions of a form input - eg. sort by..., only 
show date range..... it works well

(Continue reading)

Fabien MARTY | 2 May 09:53 2002
Picon

Re: Contributing / DB_Object

(I hope I don't post twice but my smtp server seems to have problems)

(tomas about db_oo)
> Very nice class indeed. I could share some code to add AND/OR SQL
> functionality. My fear with that classes is the support for JOIN/UNIONs,
> do that class support them?

( <at> see Alan mail for db_oo)

DB_Object support them because when you do a 'SELECT' operation, it's you who
write the SQL query. And it works fine if the result is not a mix of the two
tables. Example :

table user :
id
name
email
id_group

table user_group :
id
name

to make groups of users. Supposing that we have the corresponding classes :

class user {
var $id;
var $name;
var $email;
var $id_group;
(Continue reading)

Fabien MARTY | 2 May 09:59 2002
Picon

Re: RFI: DB_OO? Was [PEAR-DEV] Contributing / DB_Object

(I hope i don't post twice but my smtp server seems to have problems)

(alan)
> There are a number of questions that need answering before it goes in
> PEAR: Name? - having looked at JDO (Java Data Objects), it almost be
> cheeky to call it PBDO (Php DataBase Object) as it appears to do alot of
> similar thing.. - I'm game for ideas..
> DB_OO
> DB_Object
> DB_PDO
> DB_DataObjects   (I quite like this...)

Yes the last one is quite good. Another idea :

DB_To_Object or DB_2_Object
(maybe more general, so it's easy to add new concepts or ideas)

like :

DB_To_Object
  |
  |---- Lite (new name for DB_Object)
  |
  |---- PDO (new name for db_oo)
  |
  (...)

Fabien

--

-- 
(Continue reading)

Peter Bowyer | 2 May 20:20 2002

Re: [metabase-dev] MDB benchmarks

Congratulations Lukas!

Peter.

At 06:33 PM 5/2/02 +0200, Lukas Smith wrote:
>well I finally sat down and did some benchmarks with MDB.
>At first they were very disappointing but after 2 hours of tweaking MDB
>ias doing quite well.

--

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php


Gmane