c02625f0d7
Preparing for 1.7-SNAPSHOT development.
2014-05-20 18:37:46 +00:00
832f934faf
Preparing for depot-1.6.3 release.
2014-05-20 18:34:06 +00:00
d45af7c98c
Depend on samskivert 1.7.4..
2014-05-20 18:33:19 +00:00
3906c69a88
Liaison now handles exceptioning for us.
2014-05-02 20:46:36 +00:00
f2be63ec19
Choke usefully if we can't obtain last inserted id.
2014-05-02 20:14:43 +00:00
800add9667
Clean up imports.
2014-05-02 18:28:50 +00:00
9ebd2c677c
Use new smarter DatabaseLiaison.lastInsertedId.
2014-05-02 18:19:51 +00:00
2cf224dd18
Whoops! My last edit didn't actually work, it ended up falling back.
...
This works, but mdb is going to move the special caseyness inside the Liaison.
2014-05-02 18:12:46 +00:00
1a9fc404ba
Ok, this works on both mysql and postgres.
...
On mysql the column name ends up being "GENERATED_KEY".
2014-05-02 01:31:58 +00:00
e2a9702c46
This getGeneratedKeys business doesn't seem to work for us on mysql.
...
Trying a catch/fallback. This should at least provide a workaround for now...
2014-05-01 23:01:55 +00:00
e08911369e
Only use RETURN_GENERATED_KEYS on inserts.
...
This works around "unsophisticated" Postgres JDBC drivers which blindly tack
"RETURNING *" onto a query if RETURN_GENERATED_KEYS is supplied.
2013-11-20 19:45:24 +00:00
ca4ec1f4d3
Reverse order in addAll(List,Cons).
...
This causes the elements of the list to match the original order they were
added to the cons list (which stores elements "backwards").
This order matters for joins, as Ray discovered.
2013-10-10 22:06:34 +00:00
1547c7d44c
[maven-release-plugin] prepare for next development iteration
2013-09-17 19:11:08 +00:00
7e1f8d4230
[maven-release-plugin] prepare release depot-1.6.2
2013-09-17 19:11:04 +00:00
99a4d7a18e
Only rewrite record file if it changed.
2013-09-17 19:07:19 +00:00
bc8a18dec5
Factor the logic of genrecord from the Ant harness.
2013-09-17 19:07:16 +00:00
58ede042a6
Fixed some use of wrong log helper.
2013-05-24 18:45:26 +00:00
8a74276caf
Various tidyings.
2013-05-24 18:30:57 +00:00
952d01c55b
Info -> debug for initial version record message.
...
It's not that important. We already log a message indicating that we created
the table for the first time, which will always follow this message.
2013-05-24 18:30:53 +00:00
1bee1d0351
Revamp identity value generator to use Statement getGeneratedKeys.
...
Most JDBC drivers have supported this for ages. No longer do we need the
hackery of turning around and doing another query to obtain generated key
values.
2013-05-16 18:42:16 +00:00
81c24f56bf
Fix rawtypes.
2013-05-16 18:42:13 +00:00
0b5369fd11
Do this cast in a way that Java 7 doesn't complain about.
2013-05-16 18:42:09 +00:00
0c26a26ce0
Bump HSQLDB to 2.9, fix test that assumed count(*) returned int.
2013-05-16 18:42:05 +00:00
e468e2937a
Add nexus-staging-maven-plugin; makes releases easier.
2013-05-08 23:33:03 +00:00
f3b7af452d
[maven-release-plugin] prepare for next development iteration
2013-05-07 19:54:03 +00:00
1f0a64b8e3
[maven-release-plugin] prepare release depot-1.6.1
2013-05-07 19:53:59 +00:00
8803b2de12
Use latest guava and samskivert.
2013-05-07 19:51:36 +00:00
c340e7062d
Use normal Guava.
2013-05-07 19:39:37 +00:00
4af2b7c95d
More inline comments explaining why we don't just drop the DKE.
2013-05-07 00:41:17 +00:00
ce3a340199
Bugfix: store() should never throw a DuplicateKeyException.
...
It would be extremely rare, but if two nodes were trying to simultaneously
store() the same record with the same Key, one could fail with a DKE.
Attempt a second 'update' if the insert fails.
2013-05-07 00:03:05 +00:00
c63ce0c10e
Out with arrays, in with collections.
2013-05-06 18:19:31 +00:00
a625c831ae
Updates to work with HSQLDB 2.2.4.
...
We need the HsqldbLiaison fixes from samskivert 1.8-SNAPSHOT and we have to nix
some hardcoded bogosity in our own tests.
2013-05-06 17:38:16 +00:00
959dbacb53
[maven-release-plugin] prepare for next development iteration
2012-10-09 19:15:33 +00:00
e6072acae9
[maven-release-plugin] prepare release depot-1.6
2012-10-09 19:15:26 +00:00
5afad5b6b3
Move to samskivert 1.7 and guava-jdk5 13.0
2012-10-03 00:24:17 +00:00
9614fc02b9
This note has been obsolete since r376. Removed.
2012-08-13 17:56:37 +00:00
2a81514ae7
Use the right classpath in genrecord.
2012-07-25 16:38:46 +00:00
7f839f8ddd
Patch from Mike T to support parameterized types in genrecord.
2012-07-25 16:38:43 +00:00
42e8d6e75e
According to Javadoc, getColumnLabel is the method that is meant to respect the 'as foo' construct we rely on.
2012-07-03 23:38:35 +00:00
f7d7c586c0
Make GenRecordTask only honor @Transient, like DepotMarshaller.
...
We've chosen not to conflate Java transience with Depot non-persistence. It's a
little wonky to have to choose a particular memory model behavior just to have
a field not persisted in your record.
2012-06-27 18:22:36 +00:00
97be694e70
Preparing for 1.6-SNAPSHOT development.
2012-04-21 22:11:35 +00:00
c7b02449a9
Preparing for depot-1.5.3 release.
2012-04-21 22:00:46 +00:00
4734156b31
Nix unused import.
2012-04-13 18:12:51 +00:00
d254148fd0
Use ImmutableMap. I mistakenly thought we didn't use Gauva in Depot.
2012-04-13 18:12:34 +00:00
781564f9e0
A swipe of Occam's razor.
2012-04-13 16:09:02 +00:00
90d01ce58d
Revamp stock marshaller creation, use to further optimize @Transform search.
2012-04-13 16:00:51 +00:00
6d8eabce93
Improve the semantics of @Transform handling.
...
@Transform is first sought on the field itself, which overrides any other
handling. Next it is sought on the class that represents the field (i.e. if the
field is type Foo we look for an @Transform annotation on class Foo). We avoid
doing this somewhat expensive search if the field has a type that we know
cannot have an @Transform annotation. If we've still found no @Transform
annotation (which is unfortunately the overwhelmingly common case), we then
create a stock marshaller.
2012-04-13 16:00:46 +00:00
385e823b5b
Preparing for 1.6-SNAPSHOT development.
2012-04-11 02:43:52 +00:00
4d28182537
Preparing for depot-1.5.2 release.
2012-04-11 02:42:20 +00:00
946f05d3a0
Resolve our migration record during initRepos.
...
Otherwise, if a data migration is registered and run after the initialization
process, we'll end up warning that this record has not yet been initialized.
In theory, you should register your data migrations prior to calling initRepos,
but I don't want to be too draconian about that. Unlike schema migrations, you
*could* conceivably mean to start your app up and let it run before running
data migrations.
2012-04-05 22:21:37 +00:00
Ray Greenwell