No suitable drivers found

[Nikos410]

See: 6314b3c#commitcomment-135357342

Hello, I need your help with the Firebird 1.5 drive, find out that the base is connected but when performing a search in the tables it does not open and the following information appears
"No suitable drivers found for jdbc:firebirdsql://192.168.100.2:3050//home/bases/basedados_master.fdb?encoding=ISO8859_1"

and also
"Attention: :firebird driver is using Honey SQL 1. This method is deprecated in 0.46.0 and will be deleted in a future release."
Thank you very much in advance for your help.

We might have to some chores and update some of the methods mentioned in https://github.com/metabase/metabase/blob/master/docs/developers-guide/driver-changelog.md

[Nikos410]

Hey @AntoninoRocha can you reproduce the issue with a Firebird 3+ database or does it only happen with firebird 2(.5)?

[Nikos410]

Also, which Metabase version are you running? I assume the latest?

[Michael-1Mueller]

Today I tested this again in Windows, my yesterdays comment was on Docker. I have the same problem on Win.
To we need to place the jbird driver somewhere? I am using FB 2.5.7 But it actually doesent matter what I type in the massage comes allways, as soon I typed in something in the initial field an hit save.

[Michael-1Mueller]

I got it working on 0.4.7.10 So it seams to be a problem with the later versions.
The log has endless deprecation warnings
2024-01-04 16:19:16,820 WARN query-processor.deprecated :: Warnung: Treiber :firebird verwendet Honey SQL 1. Diese Methode wurde in 0.46.0 abgelöst und wird in künftigen Releases entfernt.

Wich means firebird using Honey SQL 1 which is deprecated from 4.6.0

[gilsonwindsoft]

Same problem here.

[firstDismay]

When I try to connect a Firebird 2.5 database file, version Metabase 0.48.2 driver 1.5.0, I also get a message, driver not found(It is in the list):

Metabase[3302179]:         at clojure.core$binding_conveyor_fn$fn__5823.invoke(core.clj:2047)
янв 11 10:48:25 localhost Metabase[3302179]:         at clojure.lang.AFn.call(AFn.java:18)
янв 11 10:48:25 localhost Metabase[3302179]:         at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
янв 11 10:48:25 localhost Metabase[3302179]:         at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
янв 11 10:48:25 localhost Metabase[3302179]:         at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
янв 11 10:48:25 localhost Metabase[3302179]:         ... 1 more
янв 11 10:48:25 localhost Metabase[3302179]: 2024-01-11 10:48:25,790 DEBUG middleware.log :: POST /api/database 400 7,0 ms (0 вызовы БД)
янв 11 10:48:25 localhost Metabase[3302179]: {:message "No suitable driver found for jdbc:firebirdsql://111.111.111.111:/C:\\\\xxxx\\\\xxxxx\\\\xxxxx.GDB"}

I can provide more complete logs, I don’t want to litter the thread.
PS:
It turns out that the difference in the internal structure of the drivers of the main versions of the metabase requires the presence of several driver assemblies, starting with the version that you plan to support 46.x, 47.x, 48.x, 49.x, this should be indicated in the assembly description drivers or have one universal driver that takes into account the version of the calling Metabase. The second option seems more complicated. I'm using version 48.x. I have conditions for testing the driver on Firebird 3.x and 2.5.x versions for Windows

[tsbth]

Same problem here

[Angry-Engineer]

Have the same problem

[Nikos410]

Hello everybody, sorry for the delay. We are not actively using Firebird databases anymore, so we had to find time to take a look at this issue. If anyone wants to step up as maintainer, feel free to hit me up :)

That being said, I've updated a few methods that have been deprecated / removed. Please try the attached version of the driver and let me know if it works again :)

firebird.metabase-driver-1.6.0-RC1.tar.gz

[firstDismay]

Thanks for your time Nikos.
I was able to create a connection to a FireBird 2.5 database installed on Windows from Metabase 0.48.3. But I don't see any tables. I also see an error message in the connection string:
"Invalid connection string 111.11.111.111:/C:\\\\zzz\\\\zzz\\\\zzz.GDB, reason: Port separator: ':' at beginning or end of: 111.11.111.111: [SQLState:08001, ISC error code:337248263]"}
PS: It appears that the value of the external variable port is not being processed correctly. If it is not set, the ":" delimiter is still present in the connection string, resulting in an error. If the port is installed, it still does not appear in the connection string.

[Nikos410]

@firstDismay Are you sure this is related to this issue? As far as I can see, the method for handling the connection URL did not change. Can you establish a connection when using metabase 46?

[firstDismay]

@Nikos410 Unfortunately, due to the large number of such errors, we did not pay attention to the time of their occurrence. I was misleading with my conclusions. We have connected to the database:
Firebird 2.5 WI-V2.5.9.27139
MetaBase 0.48.3
But there is not a single table. We use the system user SYSDBA.
When I click the "Synchronize Schema" button I immediately get a Metabase message:
20-01-17-MB-FB-DRV.log

[Nikos410]

@firstDismay Can you verify if these errors occur with Firebird 3+ too?