- 18 Ock, 2012 3 kayıt (commit)
-
-
Lionel Elie Mamane yazdı
-
Miklos Vajna yazdı
-
Miklos Vajna yazdı
-
- 17 Ock, 2012 37 kayıt (commit)
-
-
Bjoern Michaelsen yazdı
-
August Sodora yazdı
-
August Sodora yazdı
-
Marcel Metz yazdı
-
Marcel Metz yazdı
-
Marcel Metz yazdı
-
Marcel Metz yazdı
-
Marcel Metz yazdı
-
Marcel Metz yazdı
-
Marcel Metz yazdı
-
Michael Stahl yazdı
-
Luc Castermans yazdı
-
Michael Stahl yazdı
-
Olivier Hallot yazdı
Part XL Modules sw
-
Michael Meeks yazdı
-
Tor Lillqvist yazdı
-
Tor Lillqvist yazdı
-
Takeshi Abe yazdı
-
Eike Rathke yazdı
-
Eike Rathke yazdı
-
Eike Rathke yazdı
-
Thomas Arnhold yazdı
-
Stephan Bergmann yazdı
-
Andras Timar yazdı
-
Michael Stahl yazdı
Fixes the problem in offapi, where a rebuild after changing an IDL file would produce an offapi.rdb that contained the stale content of the old version of the IDL file. This was because in offapi 2 rdb files are built, offapi.rdb and types.rdb, and types.rdb is a merge of udkapi.rdb and offapi.rdb, hence it depends on offapi.rdb. Unfortunately this means that the UNOAPI_MERGE variable for types.rdb is inherited to offapi.rdb, with the result that after the workdir offapi.rdb is built from .urd files, it is overwritten by a merge of udkapi.rdb and a stale offapi.rdb from the solver.
-
Michael Stahl yazdı
-
Lionel Elie Mamane yazdı
-
Lionel Elie Mamane yazdı
-
Lionel Elie Mamane yazdı
-
Lionel Elie Mamane yazdı
Syntax supported by at least SQLite.
-
Lionel Elie Mamane yazdı
-
Lionel Elie Mamane yazdı
It makes no sense, because non-nullable columns can have NULL value. E.g. in "foo LEFT JOIN bar ON condition", the non-nullable columns of "bar" when it has no row matching "condition". Even when we are about to insert/update a row, we should not put a hard-coded value (that just happens to be the one constructed by the C++ default constructor for that type) in non-nullable columns: there is no guarantee that this value makes sense in that database's context. The database may or may not have a default value set for that column. If it has, we should leave it up to the database to set it automatically. If it has not, an error *is* the right reaction. Another place where this substitution does damage is when we refresh a row. We use the values we have read from the primary key to select the row again. So we should not mangle those, else the select returns no row and we mistakingly think the row has been deleted.
-
Eike Rathke yazdı
-
Eike Rathke yazdı
-
Eike Rathke yazdı
-
Andras Timar yazdı
-
Eike Rathke yazdı
-