Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked

Re^2: What is your favourite Linux or cross-platform database?

by Steve_BZ (Chaplain)
on Mar 25, 2010 at 16:11 UTC ( #830894=note: print w/replies, xml ) Need Help??

in reply to Re: What is your favourite Linux or cross-platform database?
in thread What is your favourite Linux or cross-platform database?

I agree about Firebird and DBD::InterBase, Firebird seems great (and on Windows it works very well with ODBC), but on Linux DBD::InterBase crashes randomly. I also tried unixODBC, but that was even worse. So it seems a little sad that what seems to be such a nice database with good support and tools, is marred by such a poor Perl interface.


  • Comment on Re^2: What is your favourite Linux or cross-platform database?

Replies are listed 'Best First'.
Re^3: What is your favourite Linux or cross-platform database?
by mje (Curate) on Mar 26, 2010 at 08:55 UTC

    Out of interest, what ODBC driver did you use and why was it so bad?

      Hi Mje,

      Well apart from the install which proved a nightmare under Kubuntu 9.04, but mysteriously cleared up under 9.10 see Installing DBD::ODBC, in the end I gave up using ODBC for the Firebird 2.1 connection because I couldn't get the DATE (and I think also number formats) to work and there were a number of other stability issues which I can't remember. Instead I used the DBI::Interbase driver, while it works, it is subject to occasional crashes, so I'd like to go back to trying ODBC, if it turned out to be more stable.

      My current main ODBC problem is that if I use isql on employee.fbd, (eg select first 1 change_date from salary_history), I get:

      1992-12-15 00:00:00. (Data type TIMESTAMP)

      if I use it on my own database, (eg select first 1 att_patient_examination_dtd from tbl_patient_exam), I get:

      22256-10-18. (Data type DATE)

      Any ideas what I could do?

      Surely the DATE format should work? Other applications like Flamerobin have no such problems on the same field and they don't crash either.



        I see I commented on the thread you mention and I would not describe it as a nightmare. DBD::ODBC needs an ODBC driver manager but as it is XS code it also needs the driver manager header files. Many Linux distributions distribute the header files in different packages and you hadn't installed the development package.

        I cannot say why isql is returning a timestamp but I'd guess this is down to the ODBC driver and not unixODBC or DBD::ODBC (neither of which change data types). Many bugs in ODBC drivers are attributed to earlier elements of the ODBC stack, e.g., isql perhaps in this case or unixODBC or DBD::ODBC. I'm guessing when you see a date, you are not using the ODBC driver.

        It may also help to know which ODBC driver you are using.

        unixODBC and DBD::ODBC have been around for years and years. I'm not going to say they are perfect and have no bugs but they are mature and pretty stable in most peoples definition of stable.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://830894]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others drinking their drinks and smoking their pipes about the Monastery: (2)
As of 2018-05-27 06:28 GMT
Find Nodes?
    Voting Booth?