@ if not specified data will be read in 1kb chunks. (Sterling)
@ Added a third argument to pg_lowrite() which is the length of
@ the data to write. (Sterling)
@ persistent connection. This is done by doing an "empty" transaction
@ on the connection (This was advised by someone from the PostgreSQL
@ core-team). If you leave transactions open on your page you will see a
@ "NOTICE: BEGIN: already a transaction in progress" message in your
@ apache error_log. This message is created by the PostgreSQL libs - we can
@ do nothing about it. (Thies)
a large object, and the pg_lotell call, which can be used to find the
current file offset for a large object (Submitted by: Adam Haberlach
<adam@newsnipple.com>).
@- Added the pg_lolseek and pg_lotell functions (Derick)
* Fixed a bug in zend_rsrc_list_get_rsrc_type()
* Switched register_list_destructors() to use
zend_register_list_destructors_ex() instead
* Updated all relevant modules to provide the resource type name
to register_list_destructors() call
* Updated var_dump() to output resource type name instead of number
@- Made resource type names visible, e.g. var_dump() and
@ get_resource_type() display "file" for file resources. (Andrei)
Fixes#5349 (but not the way reporter wants...).
# There's something in the way database_connect/close functions behave when
# implemented the way as in mysql module that I find a bit strange... because
# of that extra zend_list_addref() there to prevent default link disappearing
# if it's not assigned to variable, when it is, I guess its' reference count
# is at this point 2, I can do: open a db link and assign it to a variable,
# close the link and still use it afterwards.
- So here is the short version:
- a) Start moving to binary opens in Windows
- b) Give checkuid_mode() a small face lift including the fopen-wrappers.c
- The mode to this function should at least be a #define but that is for
- another day. Anyway this whole stuff should be given more face lifts in
- the future.
