Re: [firebird-support] CentOS Linux 7 (Core): Can't connect through network(local and remote)
Hi, do you have "changeDBAPassword.sh" script among installed Firebird files (bin folder)? Can you try to set SYSDBA's password with it and try again? Kind regards, Karel Rys >>> "bouberl...@yahoo.fr [firebird-support]" 4.9.2019 11:55 >>> Hi all, I am new on Firebird usage but i am facing a problem with the local network connection. After trying to apply all the suggestions from the firebird Quick Start guide and other online declarations, the same issues remains. I have already opened the firewall port 3050 for tcp. Firebird Config: DatabaseAccess = Full Providers = Remote,Engine12,Loopback RemoteServiceName = gds_db IPv6V6Only = 0 ServerMode = Classic Results of commands: connect 3C-A9-F4-5B-24-2C:employee user SYSDBA password masterkey; Statement failed, SQLSTATE = 28000 Your user name and password are not defined. Ask your database administrator to set up a Firebird login. Same results with the localhost attempt: SQL> connect localhost.localdomain:employee user SYSDBA password masterkey; Statement failed, SQLSTATE = 28000 Your user name and password are not defined. Ask your database administrator to set up a Firebird login. Any help will be appreciate Sincerely, [Non-text portions of this message have been removed]
SV: [firebird-support] index use when using order by
Hi. I couldn't agree more, and for two reasons: 1. Is it obvious to all that this is required to avoid a severe performance penalty? It wasn't to me, thats for sure. 2. Adding indices to tables (especially those heavy on writing records), is also a performance concern. So it's a bit like choosing between two evils. Best regards Mikkel Andersen Fra: firebird-support@yahoogroups.com Sendt: 18. september 2019 08:04 Til: firebird-support@yahoogroups.com Emne: Re: [firebird-support] index use when using order by On 2019-09-18 06:46, liviuslivius liviusliv...@poczta.onet.pl [firebird-support] wrote: > Hi > > your problem is that you have ascending index, which is not usable in > descending queries. You need to create descending index and it then > can be used in e.g. max queries. Ascending index is used in min > queries and order by xx asc. This is in my opinion an annoying limitation of Firebird. The indexes are theoretically bidirectional, but aren't used that way because of how index pages are written. The write strategy makes it possible for a reverse read to miss index pages when the index is modified (page split) while it is read. I think there must be a strategy that can be used to address that. In other database an 'ascending' index can also be used for descending reads, there ascending and descending are applied to individual columns to create different key orderings in the index. Mark
