| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
* This fixes adding and updating user profiles in MySQL on platforms that have a commas as a decimal separator
* Thanks Tommil!
|
| |
|
|
|
|
|
|
|
|
| |
locks to just before the try/catch/finally block, so that an exception
thrown between taking the lock and entering the try doesn't leave a mutex
locked
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Added lookup in the data-layer
- MySQL works
- SQLite doesn't have a grid-db, so it won't work there
- I added MSSQL-code to the best of my knowledge; but I don't know MSSQL :-)
- Added the plumbing up to OGS1GridServices. This speaks with the grid-server
via XMLRPC.
- Modified MapSearchModule to use the new data. It's backward compatible; if
used with an old grid-server, it just returns one found region instead of a
list.
- Refactored a bit.
Note: This updates data, grid-server and region code. No new files.
|
|
|
|
|
|
|
| |
Thank you, RuudL, for a patch that brings MSSQL up to the same
implementation level as MySQL.
|
|
|
|
|
|
|
| |
Thank you, Xugu Madison and ChrisDown, for a patch that
fixes linux filename extensions from .Xml back to .xml
|
|
|
|
|
|
|
| |
* This is a HUGE OMG update and will definitely have unknown side effects.. so this is really only for the strong hearted at this point. Regular people should let the dust settle.
* This has been tested to work with most basic functions. However.. make sure you back up 'everything' before using this. It's that big!
* Essentially we're back at square 1 in the testing phase.. so lets identify things that broke.
|
|
|
|
|
| |
* In theory, login and a large number of grid functions should now at least be multithreaded.
|
| |
|
|
|
|
|
|
| |
PluginLoader. Fix issue 1871.
|
|
|
|
| |
attributes to external XML files. Fix issues 1682 and 1786.
|
|
|
|
| |
(issue 1763).
|
| |
|
|
|
|
| |
kerunix_Flan!
|
|
|
|
| |
files. Thanks kerunix_Flan!
|
|
|
|
|
|
| |
Add migration support to gridstore.
|
| |
|
| |
|
|
|
|
| |
ASCIIEncoder in places we shouldn't.
|
|
|
|
|
|
|
|
| |
settings as when an inventoryitems table is newly created
* Normalize logging titles in database code, though this doesn't yet cover invoking code
|
|
|
|
| |
(this took a while to run).
|
|
|
|
|
| |
:: Believe it or not, but INSERT/UPDATE is actually a better pattern than REPLACE, since, with INSERT/UPDATE you can catch erroneous UPDATES to non-INSERTed items as well as catch erroneous re-INSERTS. in 95% of the cases, you SHOULD have a clear INSERT context, and a clear and separate UPDATE context. If you think your case falls within the 5%, maybe you should re-evaluate your code. ::
|
| |
|
|
|