Recent changes to bugs

Build failed on riscv64: cannot guess build type; you must specify one.

2024-10-01T03:16:32.031000Z

I am trying to package libdbi for a Linux distro on riscv64 architecture.
Using the latest release, got a build error, configure: error: cannot guess build type; you must specify one.
It was caused by outdated config.guess and config.sub files in the latest release.

Any plans to make new release?

2019-05-25T19:04:44.970000Z

I think that it would be good to make new release with updated code base :)

build system: --docdir is not honored

2018-09-09T01:58:06.045000Z

Hello,

While packaging libdbi for GNU Guix I discovered that passing --docdir=/some/doc/dir had no effect on the location of the installed doc. After digging a bit it seems this is caused by the variable being overriden in Makefile.am:

docdir = $(datadir)/doc/$(PACKAGE)-$(VERSION)

Replacing this by

docdir = @docdir@

fixes the issue.

Thanks,

Maxim

#15 dbd_parse_datetime uses time_t

2013-10-06T02:25:40.806000Z

Should be pretty simple: You just need to pinch the 64-bit gmtime code from FreeBSD. It's all implementation detail in libdbi, because your time function returns a struct tm, not a time_t, so it's transparent to callers as long as it works.

#15 dbd_parse_datetime uses time_t

2013-10-05T23:16:35.319000Z

...or suggest a fix that works on all supported OSes without breaking backwards compatibility.

#15 dbd_parse_datetime uses time_t

2013-10-05T22:46:39.593000Z

Wrong answer from a library provider. I guess we (Gnucash) will have to find a different SQL abstraction library, because we're not going to drop support for the OSes that most of them use.

#15 dbd_parse_datetime uses time_t

2013-10-05T22:25:13.334000Z

status: open --> wont-fix
assigned_to: Markus Hoenicka

dbd_parse_datetime uses time_t

2013-09-17T17:44:24.699000Z

Which most systems, even 64-bit ones, still define as a 32-bit int, which overflows in 2038. This is a widely-known bug.

25 years might seem like a long time away, but if you got a 30 year mortgage recently, you can't use dbi_conn_result_get_datetime() to retrieve the end-date from a database.

dbd_parse_datetime uses time_t

2013-09-17T17:44:24.699000Z

Ticket 15 has been modified: dbd_parse_datetime uses time_t
Edited By: Markus Hoenicka (mhoenicka)
Status updated: u'open' => u'wont-fix'
Owner updated: None => u'mhoenicka'

dbi_conn_error not reentrant

2012-07-03T08:53:13Z

Just thought I would finally file this one which could be fixed for the next release:

The static errmsg in dbi_conn_error prevents the function from being used in a multithreaded context.
It clearly crashes when 2 or more threads (each having their own dbi_conn) try to get the error message simultaneously.

I guess the simplest solution is to allocate it and force the user to free it, but all existing code will have a memory leak...
Another good solution is to add a char * full_err_msg in the dbi_conn_t, so that it becomes thread safe for different connections, and it avoids the memory leak or an api change.