Date: 10/26/99
- Next message: ak <email protected>: "Re: [PHPLIB-DEV] oohforms bad escape sequence"
- Previous message: Kristian Koehntopp: "[PHPLIB-DEV] session.inc and special characters in strings"
- In reply to: ak <email protected>: "[PHPLIB-DEV] no_next_fetch in db_oracle.inc"
- Next in thread: Kristian Köhntopp: "Re: [PHPLIB-DEV] no_next_fetch in db_oracle.inc"
- Reply: Kristian Köhntopp: "Re: [PHPLIB-DEV] no_next_fetch in db_oracle.inc"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
hi,
[skipped]
ak <email protected> wrote:
>
> But ora_no_next_fetch is never used. Instead no_next_fetch is used,
> for example in next_record(). Consequently no_next_fetch isn't defined
> at the start of that function. Maybe not a problem with php, as
> previous declaration isn't necessary. But it makes me nervous to get
> lots of php warnings. And obviously there is some inconsistence, may it be
> harmful or not.
>
> Would a change to "var $no_next_fetch=false;" be the right thing to
> do?
>
Yes, it would. BTW, I don't get any warnings concerning this variable, so
I didn't notice this mistake.
Anyway, I don't have CVS write access to PHPLIB, so I can't correct it.
Regards,
KIR
-
PHPLIB Developers Mailing List. Send messages to <phplib-dev <email protected>>.
To unsubscribe, send "unsubscribe" to <phplib-dev-request <email protected>> in
the body, not the subject, of your message.
- Next message: ak <email protected>: "Re: [PHPLIB-DEV] oohforms bad escape sequence"
- Previous message: Kristian Koehntopp: "[PHPLIB-DEV] session.inc and special characters in strings"
- In reply to: ak <email protected>: "[PHPLIB-DEV] no_next_fetch in db_oracle.inc"
- Next in thread: Kristian Köhntopp: "Re: [PHPLIB-DEV] no_next_fetch in db_oracle.inc"
- Reply: Kristian Köhntopp: "Re: [PHPLIB-DEV] no_next_fetch in db_oracle.inc"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

