DataObjects

Settings | Report Duplicate

2

I Use This!

Inactive

Commits : Listings

Analyzed 1 day ago. based on code collected 3 days ago.

Commit Message	Contributor	Files Modified	Lines Added	Lines Removed	Code Location	Date
Feb 22, 2025 — Feb 22, 2026 Showing page 55 of 100 Search / Filter on:
Remove apparently unnecessary header that can cause problems	Dirkjan Bussink	More...				about 17 years ago
Remove apparently unnecessary header that can cause problems	Dirkjan Bussink	More...				about 17 years ago
Remove apparently unnecessary header that can cause problems	Dirkjan Bussink	More...				about 17 years ago
Fixed bug with native gem generation.	Earle Clubb	More...				about 17 years ago
Fixed bug with native gem generation.	Earle Clubb	More...				about 17 years ago
support for special characters through toString -> getUnicodeValue in Command.java	Nick Chistyakov	More...				about 17 years ago
support for special characters through toString -> getUnicodeValue in Command.java	Nick Chistyakov	More...				about 17 years ago
support for special characters through toString -> getUnicodeValue in Command.java	Nick Chistyakov	More...				about 17 years ago
support for special characters through toString -> getUnicodeValue in Command.java	Nick Chistyakov	More...				about 17 years ago
Display the object type when quoting is not permitted	Dan Kubb	More...				about 17 years ago
Display the object type when quoting is not permitted	Dan Kubb	More...				about 17 years ago
Display the object type when quoting is not permitted	Dan Kubb	More...				about 17 years ago
Display the object type when quoting is not permitted	Dan Kubb	More...				about 17 years ago
Use DO::URI#query instead of query_values	Dirkjan Bussink	More...				about 17 years ago
Use DO::URI#query instead of query_values	Dirkjan Bussink	More...				about 17 years ago
fixed extended characters encoding support for jruby	Nick Chistyakov	More...				about 17 years ago
fixed extended characters encoding support for jruby	Nick Chistyakov	More...				about 17 years ago
fixed extended characters encoding support for jruby	Nick Chistyakov	More...				about 17 years ago
fixed extended characters encoding support for jruby	Nick Chistyakov	More...				about 17 years ago
Whoops, left something in there	Dirkjan Bussink	More...				about 17 years ago
Whoops, left something in there	Dirkjan Bussink	More...				about 17 years ago
Only use constants if they're really available	Dirkjan Bussink	More...				about 17 years ago
Only use constants if they're really available	Dirkjan Bussink	More...				about 17 years ago
Cleanup do_sqlite3 usage of open_v2	Dirkjan Bussink	More...				about 17 years ago
Cleanup do_sqlite3 usage of open_v2	Dirkjan Bussink	More...				about 17 years ago
Fixed tabs (converted to spaces).	Ognen Ivanovski	More...				about 17 years ago
Fixed tabs (converted to spaces).	Ognen Ivanovski	More...				about 17 years ago
[do_jdbc] Add ability to get use Reader#row_count. That value is obtained during executing reader using scrollable RS if driver supports that. The only jdbc driver doesn't support scrollable RS is SQLite3. Drivers that don't provide scrollable RS use dirty trick/hack to obtain numer of rows. I think counting rows should be moved to row_count method and numer of rows should be counted only in first invocation of row_count method (lazily). Programmers that use cursor (Reader#next) don't need to know number of rows.	pietia	More...				about 17 years ago
[do_jdbc] Add ability to get use Reader#row_count. That value is obtained during executing reader using scrollable RS if driver supports that. The only jdbc driver doesn't support scrollable RS is SQLite3. Drivers that don't provide scrollable RS use dirty trick/hack to obtain numer of rows. I think counting rows should be moved to row_count method and numer of rows should be counted only in first invocation of row_count method (lazily). Programmers that use cursor (Reader#next) don't need to know number of rows.	pietia	More...				about 17 years ago
- do_sqlite3 now uses sqlite3_open_v2() if it is compiled against sqlite >= 3.5.0 - in such case the following query_options will be honoured and passed to sqlite_open_v2 - read_only => SQLITE_OPEN_READ_ONLY - read_write => SQLITE_OPEN_READ_WRITE - create => SQLITE_OPEN_CREATE - no_mutex => SQLITE_OPEN_NOMUTEX - full_mutex => SQLITE_OPEN_FULLMUTEX - see http://www.sqlite.org/c3ref/open.html for more details - example: sqlite3://path/to/file.db?read_only=true will open that connection in read only mode - in case sqlite is < 3.5.0 these flags are silently ignored - added specs to cover this - added DataObjects::Sqlite3.sqlite3_version method that returns the sqlite3 version in use	Ognen Ivanovski	More...				about 17 years ago

←
1
2
…
51
52
53
54
55
56
57
58
59
…
99
100
→