||*()*|| Hi, Gabor.
>>>I hesitate, since this one is more compact, while it might lead to
>>>misunderstanding.
>>
>> I tend to agree.
>>
>> With that, should the stylesheets be modified to say, insert a hard
>> line break or should I use a heading above each ?
>> I personally would prefer rende
I hesitate, since this one is more compact, while it might lead to
misunderstanding.
I tend to agree.
With that, should the stylesheets be modified to say, insert a hard
line break or should I use a heading above each ?
I personally would prefer rendering like , where a line
break is inserted afte
Should I stick with the current use of two nodes? or
could I combine them with something like this,
SQLiteResult, SQLiteUnbuffered
arrayfetch
intresult_type
booldecode_binary
The current markup in the docs is more verbose, while the above is more
compact. A
> I hesitate, since this one is more compact, while it might lead to
> misunderstanding.
I tend to agree.
With that, should the stylesheets be modified to say, insert a hard
line break or should I use a heading above each ?
I personally would prefer rendering like , where a line
break is inserte
Hello all,
I've ran into an issue in the SQLite docs with regards to
. If you take a look at
http://php.net/sqlite_fetch_array (use a mirror with the recent build of
the manual), note the two class/method definitions.
The current stylesheets do not render this very pretty ;) SQLite uses
two cla
