Subject | RE: [ib-support] Connection string bug?? |
---|---|
Author | Colin Fraser |
Post date | 2001-03-25T23:26:27Z |
p.s.
My last question may have sounded a bit negative in regards to the bugs...
Please note that I love the idea of open discussion of bugs... I would far
rather they be brought out into the open than hidden away behind corporate
walls and only told to those who come with problems :-)
Regards
Colin
-----Original Message-----
From: Colin Fraser [mailto:Colin.Fraser@...]
Sent: Monday, 26 March 2001 10:56 am
To: IB Support (E-mail)
Subject: [ib-support] Connection string bug??
Hi,
I am just wondering if we should switch to IB 6 (or Firebird??) before we
push out our next app.
I was wondering how stable IB 6 is at present... do people recommend using
it in its present state for production systems, or should I keep to IB 5.6.
To help me make up my mind I had a quick look at the registered bugs on the
Firebird site... one that scared me a little was bug Id 230, SF Id 113642,
Win 32 accepts ambiguous TCP/IP connect strings. Quoting from the summary
description it says that:
"Win 32 allows clients to connect with either servername:c:<localpathname>
or servername:c:\<localpathname>. If connected clients have connected with a
mixture of these string formats, the database is treated as if it were
multiple databases and corruptions occur."
My first thought to this was... WOW, surely this is a serious (high
priority) bug...
If just connecting with different strings can cause a database corruption
then surely this should be considered major?
Do other versions of IB have this bug... IB 5.6? Borland's IB 6 release?? If
so... I am off to check all our client's connection strings!!
Regards
Colin
######################################################################
Attention:
The information in this email and in any attachments is confidential.
If you are not the intended recipient then please do not distribute,
copy or use this information. Please notify us immediately by return
email and then delete the message from your computer.
Any views or opinions presented are solely those of the author.
######################################################################
To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
######################################################################
Attention:
The information in this email and in any attachments is confidential.
If you are not the intended recipient then please do not distribute,
copy or use this information. Please notify us immediately by return
email and then delete the message from your computer.
Any views or opinions presented are solely those of the author.
######################################################################
My last question may have sounded a bit negative in regards to the bugs...
Please note that I love the idea of open discussion of bugs... I would far
rather they be brought out into the open than hidden away behind corporate
walls and only told to those who come with problems :-)
Regards
Colin
-----Original Message-----
From: Colin Fraser [mailto:Colin.Fraser@...]
Sent: Monday, 26 March 2001 10:56 am
To: IB Support (E-mail)
Subject: [ib-support] Connection string bug??
Hi,
I am just wondering if we should switch to IB 6 (or Firebird??) before we
push out our next app.
I was wondering how stable IB 6 is at present... do people recommend using
it in its present state for production systems, or should I keep to IB 5.6.
To help me make up my mind I had a quick look at the registered bugs on the
Firebird site... one that scared me a little was bug Id 230, SF Id 113642,
Win 32 accepts ambiguous TCP/IP connect strings. Quoting from the summary
description it says that:
"Win 32 allows clients to connect with either servername:c:<localpathname>
or servername:c:\<localpathname>. If connected clients have connected with a
mixture of these string formats, the database is treated as if it were
multiple databases and corruptions occur."
My first thought to this was... WOW, surely this is a serious (high
priority) bug...
If just connecting with different strings can cause a database corruption
then surely this should be considered major?
Do other versions of IB have this bug... IB 5.6? Borland's IB 6 release?? If
so... I am off to check all our client's connection strings!!
Regards
Colin
######################################################################
Attention:
The information in this email and in any attachments is confidential.
If you are not the intended recipient then please do not distribute,
copy or use this information. Please notify us immediately by return
email and then delete the message from your computer.
Any views or opinions presented are solely those of the author.
######################################################################
To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
######################################################################
Attention:
The information in this email and in any attachments is confidential.
If you are not the intended recipient then please do not distribute,
copy or use this information. Please notify us immediately by return
email and then delete the message from your computer.
Any views or opinions presented are solely those of the author.
######################################################################