Subject | RE: [ib-support] All about different connection strings? |
---|---|
Author | Alan McDonald |
Post date | 2002-11-02T10:37:37Z |
My approach has always been to use TCP naming convention
server:drive:/path/filename.gdb
I have never had a problem associated with this form.
it matters not whether you use localhost or 127.0.0.1 or someothername (as
long as it can be resolved) or some other IP address.
by being able to be resolved, this means, either the use of HOSTS file or
DNS.
local connections should not be relied on using just the drive and path
because this can end up using netbeui protocol. If you stick to the TCP
convention, you will force the use of TCP/IP and therefore have a most
reliable connection. Even when creating DSN's for IIS, you should use TCP
naming convention since IIS will only use TCP to connect.
I have no idea where some people got the idea to place spaces into a
connection string.
Alan
-----Original Message-----
From: Thomas Steinmaurer [mailto:ts@...]
Sent: Saturday, 2 November 2002 9:29
To: Ib-Support
Subject: [ib-support] All about different connection strings?
Hi all,
does someone know what InterBase treats as different connection
strings, which can lead to database corruption.
Surely, one combination is:
c:databases\data.gdb vs. c:\databases\data.gdb
But what about the following?
- local vs. remote connection (IP address)
e.g.: c:\databases\data.gdb vs. 127.0.0.1:c:\databases\data.gdb
- local vs. remote connection (the "real" IP address)
e.g.: c:\databases\data.gdb vs. 192.168.0.100:c:\databases\data.gdb
- local vs. remote connection (server name)
e.g.: c:\databases\data.gdb vs. localhost:c:\databases\data.gdb
- local vs. remote connection (the "real" server name)
e.g.: c:\databases\data.gdb vs. ntserver:c:\databases\data.gdb
- remote connection vs. remote connection
e.g.:
127.0.0.1:c:\databases\data.gdb vs. 192.168.0.100:c:\databases\data.gdb
or
localhost:c:\databases\data.gdb vs. 192.168.0.100:c:\databases\data.gdb
or
ntserver:c:\databases\data.gdb vs. 192.168.0.100:c:\databases\data.gdb
...
Is it simply the missing '\' in the database path, or can database
corruption happen when mixing local vs. remote connection.
Just thinking loud (or am I bored?). Thank you.
Regards,
Thomas Steinmaurer
IB LogManager 2.1 - The Logging/Auditing Tool for InterBase and Firebird
http://www.iblogmanager.com
Yahoo! Groups Sponsor
ADVERTISEMENT
To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
[Non-text portions of this message have been removed]
server:drive:/path/filename.gdb
I have never had a problem associated with this form.
it matters not whether you use localhost or 127.0.0.1 or someothername (as
long as it can be resolved) or some other IP address.
by being able to be resolved, this means, either the use of HOSTS file or
DNS.
local connections should not be relied on using just the drive and path
because this can end up using netbeui protocol. If you stick to the TCP
convention, you will force the use of TCP/IP and therefore have a most
reliable connection. Even when creating DSN's for IIS, you should use TCP
naming convention since IIS will only use TCP to connect.
I have no idea where some people got the idea to place spaces into a
connection string.
Alan
-----Original Message-----
From: Thomas Steinmaurer [mailto:ts@...]
Sent: Saturday, 2 November 2002 9:29
To: Ib-Support
Subject: [ib-support] All about different connection strings?
Hi all,
does someone know what InterBase treats as different connection
strings, which can lead to database corruption.
Surely, one combination is:
c:databases\data.gdb vs. c:\databases\data.gdb
But what about the following?
- local vs. remote connection (IP address)
e.g.: c:\databases\data.gdb vs. 127.0.0.1:c:\databases\data.gdb
- local vs. remote connection (the "real" IP address)
e.g.: c:\databases\data.gdb vs. 192.168.0.100:c:\databases\data.gdb
- local vs. remote connection (server name)
e.g.: c:\databases\data.gdb vs. localhost:c:\databases\data.gdb
- local vs. remote connection (the "real" server name)
e.g.: c:\databases\data.gdb vs. ntserver:c:\databases\data.gdb
- remote connection vs. remote connection
e.g.:
127.0.0.1:c:\databases\data.gdb vs. 192.168.0.100:c:\databases\data.gdb
or
localhost:c:\databases\data.gdb vs. 192.168.0.100:c:\databases\data.gdb
or
ntserver:c:\databases\data.gdb vs. 192.168.0.100:c:\databases\data.gdb
...
Is it simply the missing '\' in the database path, or can database
corruption happen when mixing local vs. remote connection.
Just thinking loud (or am I bored?). Thank you.
Regards,
Thomas Steinmaurer
IB LogManager 2.1 - The Logging/Auditing Tool for InterBase and Firebird
http://www.iblogmanager.com
Yahoo! Groups Sponsor
ADVERTISEMENT
To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
[Non-text portions of this message have been removed]