Hannes Magnusson wrote:
Do we have the technology to generate this table automatically? :)
I can't think of anything.
I suppose we could have multiple sets of xpointer() targeted xincludes
to get the info and then pre-process it with xslt to generate the
table, but that will turn ugly quickly.
On Wed, Oct 1, 2008 at 18:04, Anthony Bedford <[EMAIL PROTECTED]> wrote:
> Hannes Magnusson wrote:
>>
>> The various variations of num_rows looks awkward and confusing, all
>> the various methods and properties return exactly the same thing
>> right? So as far as the user is considered these are al
Hannes Magnusson wrote:
The various variations of num_rows looks awkward and confusing, all
the various methods and properties return exactly the same thing
right? So as far as the user is considered these are all aliases to
each other?
Yes agreed, I guess I was highlighting the fact that you c
On Wed, Oct 1, 2008 at 12:08, Anthony Bedford <[EMAIL PROTECTED]> wrote:
> Anthony Bedford wrote:
>>
>> And further to that there is another revision at:
>>
>> http://docsrva.mysql.com/public/test3.html
>>
>> I will continue to add content in an effort to find any 'edge' cases.
>>
>
> I have now co
Anthony Bedford wrote:
And further to that there is another revision at:
http://docsrva.mysql.com/public/test3.html
I will continue to add content in an effort to find any 'edge' cases.
I have now completed the process of adding content for MySQLi related
classes[1]. I haven't found anythin
On Fri, Sep 12, 2008 at 18:54, Anthony Bedford <[EMAIL PROTECTED]> wrote:
> And further to that there is another revision at:
>
> http://docsrva.mysql.com/public/test3.html
>
> I will continue to add content in an effort to find any 'edge' cases.
Looks great
-Hannes
And further to that there is another revision at:
http://docsrva.mysql.com/public/test3.html
I will continue to add content in an effort to find any 'edge' cases.
Thanks,
Tony
Anthony Bedford wrote:
Hi,
As requested I've been working on a mockup of a possible change to this
page:
http://w
Ulf Wendel wrote:
Assuming that every alias entry is somewhat deprecated and only there
for BC reasons, does it have to be in the main table (mockup), wouldn't
it be better to "hide" an alias by not showing it in the main table but
in a second table "BC/deprecated" below the main overview tab
Hannes Magnusson wrote:
On Wed, Sep 10, 2008 at 19:13, Anthony Bedford <[EMAIL PROTECTED]> wrote:
Hi,
As requested I've been working on a mockup of a possible change to this
page:
http://www.php.net/manual/en/book.mysqli.php
The mockup can be viewed here (with notes):
http://docsrva.mysql.c
On Wed, Sep 10, 2008 at 19:13, Anthony Bedford <[EMAIL PROTECTED]> wrote:
> Hi,
>
> As requested I've been working on a mockup of a possible change to this
> page:
>
> http://www.php.net/manual/en/book.mysqli.php
>
> The mockup can be viewed here (with notes):
>
> http://docsrva.mysql.com/public/te
Hi,
As requested I've been working on a mockup of a possible change to this
page:
http://www.php.net/manual/en/book.mysqli.php
The mockup can be viewed here (with notes):
http://docsrva.mysql.com/public/test2.html
This is just a simple mockup, you can ignore the colour scheme. :)
Here are
On 14 Jul 2008, at 01:34, Hannes Magnusson wrote:
On Mon, Jul 14, 2008 at 01:28, Daniel Convissor
<[EMAIL PROTECTED]> wrote:
On Sun, Jul 13, 2008 at 01:46:29PM +0200, Hannes Magnusson wrote:
On Sat, Jul 12, 2008 at 15:04, Daniel Convissor
<[EMAIL PROTECTED]> wrote:
Hi Folks:
The various htt
On Mon, Jul 14, 2008 at 01:28, Daniel Convissor
<[EMAIL PROTECTED]> wrote:
> On Sun, Jul 13, 2008 at 01:46:29PM +0200, Hannes Magnusson wrote:
>> On Sat, Jul 12, 2008 at 15:04, Daniel Convissor
>> <[EMAIL PROTECTED]> wrote:
>> > Hi Folks:
>> >
>> > The various http://php.net/mysqli_* function names
On Sun, Jul 13, 2008 at 01:46:29PM +0200, Hannes Magnusson wrote:
> On Sat, Jul 12, 2008 at 15:04, Daniel Convissor
> <[EMAIL PROTECTED]> wrote:
> > Hi Folks:
> >
> > The various http://php.net/mysqli_* function names redirects go to the
> > old mysql_* functions rather than the "new" myslqi_* func
On Sat, Jul 12, 2008 at 15:04, Daniel Convissor
<[EMAIL PROTECTED]> wrote:
> Hi Folks:
>
> The various http://php.net/mysqli_* function names redirects go to the
> old mysql_* functions rather than the "new" myslqi_* functions. Is this
> intentional?
No.
-Hannes
Hi Folks:
The various http://php.net/mysqli_* function names redirects go to the
old mysql_* functions rather than the "new" myslqi_* functions. Is this
intentional?
Thanks,
--Dan
--
T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
data intensive web and databa
On 2/11/07, Friedhelm Betz <[EMAIL PROTECTED]> wrote:
Hi Philip,
> And, should we keep track (document)
> _when_ extensions became stable?
Nice too have, but not really necessary, imho.
For PECL, the information is on the PECL website.
For php-src, it's maybe worth documenting, but it will cl
Hi Philip,
And, should we keep track (document)
_when_ extensions became stable?
Nice too have, but not really necessary, imho.
Regards
Friedhelm
This was already fixed in the English translation, so it's up
to the Germans to catch up (-:
On that note, Philip just said to me "i wonder if we can create
a way to
store "important" items across translations, like for example,
deprecated status (ex. mysqli from that thread)"
After a bit
Hello,
Philip Olson wrote:
- Original Message -
This was already fixed in the English translation, so it's up
to the Germans to catch up (-:
On that note, Philip just said to me "i wonder if we can create a way to
store "important" items across translations, like for example,
depreca
Hi,
Philip Olson wrote:
- Original Message -
This was already fixed in the English translation, so it's up
to the Germans to catch up (-:
On that note, Philip just said to me "i wonder if we can create a way to
store "important" items across translations, like for example,
deprecated
- Original Message -
This was already fixed in the English translation, so it's up
to the Germans to catch up (-:
On that note, Philip just said to me "i wonder if we can create a
way to
store "important" items across translations, like for example,
deprecated status (ex. mysqli fro
bah.. the more the entities, the slower the build becomes. So, let's not
interfere with translators work :P
Nuno
- Original Message -
This was already fixed in the English translation, so it's up
to the Germans to catch up (-:
On that note, Philip just said to me "i wonder if we can
Sean Coates wrote:
[...]
That way, this sort of thing would never happen (once the &status.foo;
entities make it into the various reference.xml files.
Thoughts?
Big +1
Friedhelm
>> This was already fixed in the English translation, so it's up
>> to the Germans to catch up (-:
On that note, Philip just said to me "i wonder if we can create a way to
store "important" items across translations, like for example,
deprecated status (ex. mysqli from that thread)"
After a bit
Ok thanks :)
I just saw that someone emailed doc-de@ before me so we should be ok soon
(hopefully).
Andi
> -Original Message-
> From: Sean Coates [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 05, 2007 9:50 PM
> To: Andi Gutmans
> Cc: [email protected]
> Sub
Hi,
> http://de3.php.net/manual/de/ref.mysqli.php
> MySQLi isn't experimental to the best of my knowledge. This was probably
> never removed.
This was already fixed in the English translation, so it's up to the
Germans to catch up (-:
S
http://de3.php.net/manual/de/ref.mysqli.php
Hey all,
MySQLi isn't experimental to the best of my knowledge. This was probably never
removed.
Keep up the good work!
Andi
On Tue, 26 Apr 2005, Gabor Hojtsy wrote:
> > Does anyone object to removing the deprecated alias function
> > files from ext.mysqli that are now mysqli_stm_* functions?
> > For example: mysqli_stmt_fetch() versus mysqli_fetch(). Then
> > the real functions will refer to the alias using
> > &info.d
Does anyone object to removing the deprecated alias function
files from ext.mysqli that are now mysqli_stm_* functions?
For example: mysqli_stmt_fetch() versus mysqli_fetch(). Then
the real functions will refer to the alias using
&info.deprecated.alias;
The question is whether depreciated functions
Hello!
Does anyone object to removing the deprecated alias function
files from ext.mysqli that are now mysqli_stm_* functions?
For example: mysqli_stmt_fetch() versus mysqli_fetch(). Then
the real functions will refer to the alias using
&info.deprecated.alias;
Regards,
Philip
Judging from 'num_rows', how would you decide if it is an sqlite,
mysqli, etc. object method?
Goba
Let's say the entry in the index would be something like:
num_rows (SQLite)
num_rows (MySQLi)
Is that OK ?
Yep, if someone has the time to look into implementing it :)
Goba
> Judging from 'num_rows', how would you decide if it is an sqlite,
> mysqli, etc. object method?
> Goba
Let's say the entry in the index would be something like:
num_rows (SQLite)
num_rows (MySQLi)
Is that OK ?
Gabriel PREDA
I switched to using MySQLi... I'm using Edit+ that has the ability to link
to the CHM version of the manual... whenever the cursor is on a function
name at CTRL+1...3..4 it will open the manual at that function...
However when using object oriened style with MySQLi this will not happen...
because t
I switched to using MySQLi... I'm using Edit+ that has the ability to link
to the CHM version of the manual... whenever the cursor is on a function
name at CTRL+1...3..4 it will open the manual at that function...
However when using object oriened style with MySQLi this will not happen...
because
Hi,
in http://www.php.net/manual/en/function.mysqli-stmt-bind-result.php it
remains unclear whether bind_result must be called after every execute
or if one call for many statements of a kind is sufficient.
I.e. I use a prepared SELECT statement:
// prepare
$stmt = $mysqli->prepare(
"SELECT ti
Aloha Enrique,
I changed the text a little bit (copied it from ext/mysql :). Thx for the
hint!
Cheers
Georg
> Hi,
>
> There is a paragraph that i don´t understand that says:
>
> If two or more columns in the result set have the same column name, the
> associative array
> returned by the mysqli_fetch_assoc function
> will contain the value of
> the last column of that name. If you must work wi
Title: mysqli-fetch-assoc
Hi,
There is a paragraph that i don´t understand that says:
If two or more columns in the result set have the same column name, the associative array
returned by the mysqli_fetch_assoc function will contain the value of
the last column of that name. If
See also
mysqli_prepare,
mysqli_stmt_errno,
mysqli_stmt_error,
mysqli_bind_result
as well as the return values, etc. I'm fine with the methodsynopsis ;)
From my view it's easier to read cause you see on first look what you
need - you don't have to read th
Gabor Hojtsy wrote:
See also
mysqli_prepare,
mysqli_stmt_errno,
mysqli_stmt_error,
mysqli_bind_result
as well as the return values, etc. I'm fine with the methodsynopsis ;)
From my view it's easier to read cause you see on first look what you
need - y
See also
mysqli_prepare,
mysqli_stmt_errno,
mysqli_stmt_error,
mysqli_bind_result
as well as the return values, etc. I'm fine with the methodsynopsis ;)
From my view it's easier to read cause you see on first look what you need -
you don't have to read th
Hi,
>
> See also
>
> mysqli_prepare,
> mysqli_stmt_errno,
> mysqli_stmt_error,
> mysqli_bind_result
>
>
> as well as the return values, etc. I'm fine with the methodsynopsis ;)
From my view it's easier to read cause you see on first look what yo
Derick Rethans wrote:
On Wed, 18 Feb 2004, Mehdi Achour wrote:
Georg used a different structure for the .xml files, here's the result :
http://www.php.net/manual/en/function.mysqli-fetch.php
Should we change the files structures for consistency ?
Just keep it until we have a good way of docum
On Wed, 18 Feb 2004, Mehdi Achour wrote:
> Georg used a different structure for the .xml files, here's the result :
>http://www.php.net/manual/en/function.mysqli-fetch.php
>
> Should we change the files structures for consistency ?
Just keep it until we have a good way of documenting OO exten
Hi folks,
Georg used a different structure for the .xml files, here's the result :
http://www.php.net/manual/en/function.mysqli-fetch.php
Should we change the files structures for consistency ?
didou
I remember the rpl functions have been removed by Georg for some reason.
You should contact Georg Richter ([EMAIL PROTECTED]) for more information on
the extension.
Goba
[EMAIL PROTECTED] wrote:
I noticed (after commiting files over dead revisions) that some of the
replication functions were re
I noticed (after commiting files over dead revisions) that some of the
replication functions were removed. Should I again remove these files
or wait for the information from MySQL about the lib?
Kenneth
heh, welcome to the wonderful issues of php-gtk..
> -Original Message-
> From: Gabor Hojtsy [mailto:[EMAIL PROTECTED]
> Sent: 22 November 2003 17:29
> To: Georg Richter
> Cc: [EMAIL PROTECTED]
> Subject: Re: [PHP-DOC] MySQLI Documentation
>
>
> >>The
But I did, see http://www.vl-srm.net/doc/class.srmapp.php (it needs a
bit of tweaking though as the constructor doesn't look good yet).
I tweaked some of the DSSSL that I copied from the PHP Doc stuff, and
backporting it is possible, it just takes a bit of time. The XML for
this is attached.
I thou
On Sat, 22 Nov 2003, Gabor Hojtsy wrote:
> >>The DOMXML extension has this kind of documentation.
> >
> > No, DOMXML only supports OO-Syntax, not OO and procedural style.
> > Also class->method is hard to read instead to have a list of properties and
> > methods for different objects.
>
> Well, th
The DOMXML extension has this kind of documentation.
No, DOMXML only supports OO-Syntax, not OO and procedural style.
Also class->method is hard to read instead to have a list of properties and
methods for different objects.
Well, the dir class has some true OO documentation, but there is not
muc
> Hi Georg!
> The DOMXML extension has this kind of documentation.
No, DOMXML only supports OO-Syntax, not OO and procedural style.
Also class->method is hard to read instead to have a list of properties and
methods for different objects.
Georg
Hi Georg!
during the last days I changed a lot in php5's ext/mysqli. Now I have some
"minor" problems:
How to document oo-syntax?
- objects
- methods
- properties
For all methods and properties there exists a procedural function too, so a
function entry s
Hi,
during the last days I changed a lot in php5's ext/mysqli. Now I have some
"minor" problems:
How to document oo-syntax?
- objects
- methods
- properties
For all methods and properties there exists a procedural function too, so a
function entry should
Gabor Hojtsy wrote:
BTW we also have a TODO item here for Hartmut. We need to have a PHP 5
version availabilty information field in the docs now, not only PHP 3
and 4. Given that MySQLi is only available for PHP 5 if I understand
correctly.
this is going to be tricky because PHP 5 is in the
same
56 matches
Mail list logo
