FWIW, when I need something like this for the WHERE part of a query I do it
with the ternary operator and a static import of ExpressionFactory (which
your IDE can add for you), like:
.and(yearRange != null ? APPOINTMENT_DATE.gt(yearRange) : expTrue())
I don't think there is a good alternative to
Same here, everything passed, so +1 although there is that weak signature.
On Tue, Jun 18, 2024 at 11:24 AM Michael Gentry wrote:
> +1
>
> All my release steps passed with the caveat of the weak signature reported
> earlier.
>
> Thanks Nikita!
> mrg
>
>
> On Fri, Jun 14, 2024 at 6:27 AM Nikita
If you’re running Java 17 or later you could use multiline strings literals
as a feature-less replacement of SQLTemplate.
On Thu, Jun 13, 2024 at 8:23 AM William Williams
wrote:
> Hey Mike,
>
> How's it going? This is related to a Velocity version vulnerability. I
> upgraded to the latest
+1 as far as the release assembly goes. I'm indifferent about waiting for
another fix.
1) verified checksums
2) verified signatures
3) verified archives are basically identical between platforms (there are
some jquery differences)
4) RAT indicates no unlicensed files
5) compiled from source
6)
I am fine with both proposals. +1
On Tue, Nov 21, 2023 at 6:10 AM Andrus Adamchik wrote:
> I am +1 on both.
>
> > On Nov 21, 2023, at 4:04 AM, Nikita Timofeev
> wrote:
> >
> > Hi all,
> >
> > Wanted to share a couple of my thoughts about changes that could be good
> > for Cayenne. And the
+1 all my checks passed.
There is one gpg key in the KEYS file that it complained about using a weak
signature:
gpg: Note: third-party key signatures using the SHA1 algorithm are rejected
gpg: (use option "--allow-weak-key-signatures" to override)
gpg: key EFBE839588C2AA2E: 1 bad signature
> [1] https://github.com/apache/cayenne/compare/4.2.RC1...4.2.RC2
>
> On Thu, Dec 1, 2022 at 10:56 PM John Huss wrote:
> >
> > All my release checks passed. Also all the unit tests in my own projects
> > pass with this release!
> >
> > I am having a pro
All my release checks passed. Also all the unit tests in my own projects
pass with this release!
I am having a problem with the Ant Cgen task - it doesn't seem to be
finding the default cgen templates anymore if they are not overridden in
the ant configuration:
On Thu, Jul 28, 2022 at 6:44 AM Nikita Timofeev
wrote:
> Hi all,
>
> I'm cleaning up project structure a bit. And I have a question about
> things that I don't use and don't really know.
>
> 1. Ant and vpp dependency. This one is really the last that prevents
> us from switching to the Maven
Sounds good. For #3 on SQLTemplate, will these still be able to be defined
in the modeler? I like being able to do that, though I only use a single
database target for the SQL.
On Fri, Jul 15, 2022 at 2:40 PM Andrus Adamchik wrote:
> Another block of ideas for 5.0. Related to expressions and
I'm good with all of that. Except we do use cayenne-web (stateless). It's
not a lot of code so we could pull it in and keep our own copy, but I
wonder how many people are using it. We're not defining the serverRuntime
in web.xml (which would be a bit limiting and clunky), but otherwise I like
the
+1
All my checks passed on the mac with Java 17.
On Mon, Jun 6, 2022 at 10:48 AM Andrus Adamchik wrote:
> All my checks pass. +1
>
> > On Jun 3, 2022, at 2:23 PM, Nikita Timofeev
> wrote:
> >
> > Hi all,
> >
> > Here is a 4.2.RC1 release as promised.
> >
> > Release notes:
>
+1
On Tue, Feb 22, 2022 at 12:36 AM Andrus Adamchik
wrote:
> +1
>
> > On Feb 22, 2022, at 4:32 AM, Aristedes Maniatis
> wrote:
> >
> > I'm thinking:
> >
> >
> > * 3.1.3 be marked on the website "EOL".
> >
> > * 4.0.2 be marked as "Security fixes only"
> >
> > * 4.1.1 be marked as "Security
+1
All my checks passed on the mac.
On Tue, Dec 21, 2021 at 2:24 AM Nikita Timofeev
wrote:
> Hi all,
>
> Here is another try of the 4.1.1 release. This time with Gradle
> upgrade and proper support for the JDK 17 in the Modeler.
>
> Release notes:
>
an't run it.
>
> Note: If on macOS you might have to give Eclipse/Terminal permissions in
> System Preferences. Also, if on Monterey, it likes to hide newly opened
> windows behind current windows. I don't have an app icon yet, so it shows
> up as a folder icon if you Comma
he video.
>
>
> On Tue, Dec 14, 2021 at 6:58 PM Lon Varscsak
> wrote:
>
> > What about an Electron app?
> >
> > On Tue, Dec 14, 2021 at 3:59 PM John Huss wrote:
> >
> > > My 2 cents is that Java desktop UI is effectively dead. So switching to
>
+1
After copying cayenne-gradle-plugin over, all my checklist passes. The
modeler starts with JDK 17 too.
On Wed, Dec 15, 2021 at 9:23 AM Nikita Timofeev
wrote:
> Hi all,
>
> Here is the 4.1.1 release. There are some useful fixes, including JDK
> 17 support in the Modeler.
>
> Release notes:
>
us/1465245360973131777>
> [3]
> https://blog.jetbrains.com/kotlin/2021/08/compose-multiplatform-goes-alpha/#toolbox
> <
> https://blog.jetbrains.com/kotlin/2021/08/compose-multiplatform-goes-alpha/#toolbox
> >
>
>
>
> > On Dec 14, 2021, at 12:48 AM, John Huss wrote:
I believe that compose UI library is used to build the new upcoming IDE
from JetBrains called Fleet. So I expect it will continue to be supported
unless that product completely flops.
I don't mind the current modeler UI. It's good enough for me.
https://www.jetbrains.com/fleet/
On Sat, Dec 11,
0 :)
>
> Andrus
>
>
> > On Dec 2, 2021, at 5:20 PM, John Huss wrote:
> >
> > After correcting the gradle issue, I'm seeing these test failures on JDK
> > 17.0.1:
> >
> > [*INFO*] *--- *maven-surefire-plugin:2.22.2:test *(default-test)*
cted. You need manually copy
> > 'cayenne-gradle-plugin/gradle' directory from the git checkout to the
> > source release.
> > Can't bundle it with the source code release due to the Apache policies.
> >
> > On Wed, Dec 1, 2021 at 9:37 PM John Huss wrote:
>
Note, I'm using java 17.0.1 on an M1 mac.
On Wed, Dec 1, 2021 at 12:34 PM John Huss wrote:
> Is there a dependency I need to install first for the gradle plugin to
> build? I'm getting this error when building:
>
> [*INFO*] *--- *exec-maven-plugin:1.6.0:exec *(gradle)* @
> cayenn
Is there a dependency I need to install first for the gradle plugin to
build? I'm getting this error when building:
[*INFO*] *--- *exec-maven-plugin:1.6.0:exec *(gradle)* @
cayenne-gradle-plugin* ---*
Error: Could not find or load main class
org.gradle.wrapper.GradleWrapperMain
Caused by:
I'm in favor of making a release.
On Tue, Nov 23, 2021 at 12:10 PM Nikita Timofeev
wrote:
> Hi all,
>
> I think Cayenne 4.2 beta is pretty ready to be released. So I want to
> give some heads up and possibly hear back if I miss something
> critical. There's been added support for the JDK 17,
Besides generating the java classes, we use cgen to generate source code
for other languages and other artifacts, using different configuration. So
while I would be in favor of removing the duplication of the configuration
for java class generation, I would still like to have the cgen task remain
Cayenne Modeler crashes on launch with JDK 17 (from Oracle). Here is the
output:
/A/C/C/MacOS> *./CayenneModeler *
2021-09-24 09:50:12.418 defaults[76618:3072366]
The domain/default pair of (kCFPreferencesAnyApplication, AppleLocale) does
not exist
./CayenneModeler: line 310: [: ==: unary
\jdk11.0.12_7
> OS name: "windows 10", version: "10.0", arch: "x86", family: "windows"
>
> On Mon, Sep 20, 2021 at 7:04 PM John Huss wrote:
> >
> > The latest master is failing to build with the distribution o
The latest master is failing to build with the distribution of OpenJDK 11
from Amazon due to a javadoc problem:
*QualifierTranslator is not public in
org.apache.cayenne.access.translator.select; cannot be accessed from
outside *
Here is the entire error:
[*ERROR*] Failed to execute goal
+1
1) verified signatures
2) verified archives are basically identical between platforms
3) RAT indicates no unlicensed files
4) compiled from source
5) unit tests ran successfully
6) macOS specific and Platform-agnostic modelers launch on macOS
On Sat, Mar 13, 2021 at 9:41 AM Nikita Timofeev
+1
1) verified signatures
2) verified archives are basically identical between platforms
3) RAT indicates no unlicensed files
4) compiled from source
5) unit tests ran successfully
6) macOS specific and Platform-agnostic modelers launch on macOS
With the caveat that I haven't been running 4.2 in
This change (in 4.1 final) causes any direct modifications to the
java.util.Set mapping the to-many relationship to be ignored, which is a
silently breaking change.
For example, this code:
myEntity.getMyRelationshipMappedAsSet().*add*(newObject);
myEntity.getObjectContext().commitChanges();
+1
1) verified signatures
2) verified archives are basically identical between platforms
3) RAT indicates no unlicensed files
4) compiled from source
5) unit tests ran successfully
6) macOS specific and Platform-agnostic modelers launch on macOS
On Tue, Jul 14, 2020 at 10:57 AM Nikita Timofeev
Yeah, I have special handling around BigDecimals to get around this. Later
on I generalized it a bit more to use Comparable.compareTo(other) == 0 to
mean there was no change. Besides BigDecimal I saw this same problem with
joda DateTime objects that had different time zones that worked out to be
I would be fine with fixing it up and remaking the release, but I don’t
know how much of a hassle that is. I can find time to fix AutoAdapter in
the next two days I think.
On Mon, Apr 13, 2020 at 1:34 PM Andrus Adamchik
wrote:
> Been thinking more about this... This breaks basic commit
+1
I got the rat 0.14 snapshot release, and everything looks good! Thanks!
1) verified signatures
2) verified archives are basically identical between platforms
3) RAT indicates no unlicensed files
4) compiled from source
5) unit tests ran successfully
6) macOS specific and Platform-agnostic
he.org/jira/browse/CAY-2652
> [2]
> https://repository.apache.org/content/repositories/snapshots/org/apache/rat/apache-rat/
>
> On Sat, Mar 28, 2020 at 1:04 AM John Huss wrote:
> >
> > Thanks.
> >
> > I figured out the problem with cgen was that I had
> velocity
eaningful
> FK really creating problems, so need to fix this.
>
> I'll keep this vote open in case something else comes up.
>
> On Thu, Mar 26, 2020 at 1:05 AM John Huss wrote:
> >
> > Thanks for all your work on this. 4.2 is going to be a great release! I
> ran
>
Thanks for all your work on this. 4.2 is going to be a great release! I ran
all my checks on the release and almost everything passed.
I don't know what changed, but I'm having a RAT problem I haven't seen
before. RAT (both 0.12 and 0.13) show this header:
Printing headers for text files without
On Wed, Dec 11, 2019 at 3:13 PM John Huss wrote:
>
>
> On Wed, Dec 11, 2019 at 1:59 PM John Huss wrote:
>
>>
>>
>> On Wed, Dec 11, 2019 at 10:59 AM Andrus Adamchik
>> wrote:
>>
>>>
>>>
>>> > On Dec 10, 2019, at 9:
On Wed, Dec 11, 2019 at 1:59 PM John Huss wrote:
>
>
> On Wed, Dec 11, 2019 at 10:59 AM Andrus Adamchik
> wrote:
>
>>
>>
>> > On Dec 10, 2019, at 9:39 PM, John Huss wrote:
>> >
>> >> My projects are set up to use soft references usi
On Wed, Dec 11, 2019 at 11:38 AM Andrus Adamchik
wrote:
>
>
> > On Dec 10, 2019, at 6:51 PM, John Huss wrote:
> >
> >>> One solution is to null out the ObjectContext on any objects that are
> >>> inserted into the Query Cache. This solves both proble
On Wed, Dec 11, 2019 at 10:59 AM Andrus Adamchik
wrote:
>
>
> > On Dec 10, 2019, at 9:39 PM, John Huss wrote:
> >
> >> My projects are set up to use soft references using "
> >> cayenne.server.object_retain_strategy=soft". I wouldn't expect this to
On Tue, Dec 10, 2019 at 9:51 AM John Huss wrote:
>
> Thanks for the feedback - I appreciate it.
>
> On Sun, Dec 8, 2019 at 3:17 AM Andrus Adamchik
> wrote:
>
>> Hi John,
>>
>> Thanks for the analysis. You've put a significant effort in this issue,
>>
medies). Let me try to clarify how I see it.
>
> > On Dec 7, 2019, at 12:09 AM, John Huss wrote:
> >
> > 1) The lifetime of entries in the Local Query Cache exceeds their
> > availability, which is the life of their ObjectContext. Any cache that is
> > not ex
Switching to the dev list:
I've had some time this week to revisit this issue with memory leaks,
especially when using the Local Query Cache. There are two separate issues
to address:
1) The lifetime of entries in the Local Query Cache exceeds their
availability, which is the life of their
log4j.logger.org.apache.cayenne.log.JdbcEventLogger=INFO
On Wed, Oct 30, 2019 at 2:32 AM Markus Reich wrote:
> Hi,
>
> since the move to slf4j I'm not able to control the log level anymore. As I
> couldn't find any documentation, my last hope is the community :-)
>
> I'm no logging expert :-/
>
+1
1) verified signatures
2) verified archives are basically identical between platforms - *however*,
there are some differences that haven't been present before - the windows
version is the only one that includes the *-frame.html files like:
doc/api/allclasses-frame.html.
There are a bunch of
dly, I think you can turn it
> to useful info in a fairly straightforward manner.
>
> Andrus
>
>
> > On Oct 11, 2019, at 10:24 AM, John Huss wrote:
> >
> > I haven't worked with the GraphDiff API much, but it's not super easy to
> > turn a GraphDiff into something im
I haven't worked with the GraphDiff API much, but it's not super easy to
turn a GraphDiff into something immediately useful.
When I've needed things like this I've usually constructed a
List> with a row for each changed object and a map with
attribute/relationship key to the new value. Looking at
+1
1) verified checksums
2) verified signatures
3) verified archives are basically identical between platforms
4) RAT indicates no unlicensed files
5) compiled from source
6) unit tests ran successfully
7) Platform-agnostic modeler launches on macOS
On Wed, Oct 9, 2019 at 11:57 AM Nikita
+1
1) verified checksums
2) verified signatures
3) verified archives are basically identical between platforms
4) RAT indicates no unlicensed files
5) compiled from source
6) unit tests ran successfully
7) Modeler launches on macOS
On Thu, Oct 3, 2019 at 9:23 AM Nikita Timofeev
wrote:
> Hi
x versions as well).
> They should be fixed eventually, but I'm not sure we should delay the
> 4.2 milestone release because of them.
>
> On Wed, Sep 4, 2019 at 5:36 PM John Huss wrote:
> >
> > I'm ready for 4.0 and 4.1 any time.
> >
> > Regarding 4.2, I reported t
I'm ready for 4.0 and 4.1 any time.
Regarding 4.2, I reported two issues a while back that haven't been
commented on yet. I'd like to see at least a sentence reply about those
since they represent test cases that started failing for me starting with
4.2.
se with a followup commit
with the fix. But maybe I'm asking for too much.
I do greatly value Cayenne and it plays a huge role in the software we
make. I am very thankful for all the people who have contributed to it's
success and continue to work to make it better.
> > On Jul 5, 2019, at 6:45 P
then
> brainstorm on how to best accomplish it.
>
> > I'm out of the office until Monday, so I can't work on it until then, but
> > we can keep discussing beforehand.
>
> Appreciate that!
>
> Andrus
>
>
> > On Jul 4, 2019, at 5:50 PM, John Huss wrote:
>
, but those didn't make it into Cayenne. And I need to write
some more to check the behavior of the shared query cache when the
localQueryCache is set.
I'm out of the office until Monday, so I can't work on it until then, but
we can keep discussing beforehand. Thanks.
> On Jul 3, 2019, at 5:34
gt; >
> > The following commit(s) were added to refs/heads/master by this push:
> > new 597376a CAY-2589 Allow optionally using a local query cache
> that is separate from the shared query cache.
> > 597376a is described below
> >
> > commit 597376ae558b9a0c5ddc4390d
Yep, Postgres.
On Tue, Jun 4, 2019 at 9:43 AM Andrus Adamchik
wrote:
> Hmm.. In theory auto-pk should be compatible with batching. Is this on
> PostgreSQL?
>
> Andrus
>
> > On Jun 4, 2019, at 5:39 PM, John Huss wrote:
> >
> > Just to follow up on this, after s
t;
> > On 29 May 2019, at 15:23, John Huss wrote:
> >
> > Doh! Turns out Cayenne already supports this for Postgres. Who knew! :-P
> >
> > 2621 [main] INFO org.apache.cayenne.log.JdbcEventLogger - INSERT INTO
> test
> > (payload) VALUES (?)
> >
> >
for the sake of PK generation feels old.
>
> Andrus
>
> > On May 28, 2019, at 6:47 PM, John Huss wrote:
> >
> > Postgresql also recently improved their support in this area (in version
> > 10). It's more like syntactic sugar on top of things you could already
>
Postgresql also recently improved their support in this area (in version
10). It's more like syntactic sugar on top of things you could already do,
but I'd be interested to know if it can be used by Cayenne in the same way
as the MySQL auto-increment columns.
The DDL syntax is supposedly an SQL
+1
1) verified checksums
2) verified signatures
3) verified archives are basically identical between platforms
4) RAT indicates no unlicensed files
5) compiled from source
6) unit tests ran successfully
7) Modeler launches on macOS
On Sat, May 4, 2019 at 7:27 AM Nikita Timofeev
wrote:
> Hi
I'm trying to generate classes using the cgen ant task and I'm getting this
error. Did this get broken or is it me?
org.apache.cayenne.di.DIRuntimeException: DI container has no binding for
key
at
org.apache.cayenne.di.spi.DefaultInjector.getProvider(DefaultInjector.java:158)
at
It must have just had a bad cache somewhere. I touched the file and rebuilt
and now it is working. ¯\_(ツ)_/¯
On Thu, May 2, 2019 at 1:26 PM Lon Varscsak wrote:
> I've compiled it against OpenJDK 11 (not Corretto) without an issue.
>
> On Thu, May 2, 2019 at 7:38 AM John Hu
May 2, 2019, at 5:10 PM, John Huss wrote:
> >
> > I'm seeing a build failure with Java 11 on the master branch (below). It
> > would be nice to get this fixed up since Java 11 has been released for a
> > while now. Thanks!
> >
> > [ERROR] Tests run: 2, F
I'm seeing a build failure with Java 11 on the master branch (below). It
would be nice to get this fixed up since Java 11 has been released for a
while now. Thanks!
[ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed:
0.166 s <<< FAILURE! - in
, Andrus Adamchik wrote:
> > Good catch. I guess since this is a dependency that can be easily
> downloaded from the internet, we can let it slip for now and proceed with
> the release (and fix it in the next release). Does anyone feel strongly
> about this one?
> >
> &g
The windows zip doesn't include the file
"lib/third-party/slf4j-api-1.7.25.jar" which the mac one does.
Otherwise it looks good.
On Fri, Mar 1, 2019 at 5:28 AM Nikita Timofeev
wrote:
> Hi all,
>
> Here is long-promised 4.1 beta release with lots of fixes and some
> minor features.
>
> Release
I ran my checks and this release looks good. +1
On Thu, Dec 20, 2018 at 7:36 AM Nikita Timofeev
wrote:
> Hi all,
>
> This is a maintenance release of 4.0 branch with minor features in
> Modeler (backported from 4.1).
>
> Maven repo:
>
In Cayenne Modeler the SQL Scripts tab for Queries has not been scrollable
vertically or horizontally for some time now, since the first all gray icon
version was introduced. Could someone please fix it?
FYI, I'm using it on Mac.
Thanks!
On Tue, Sep 25, 2018 at 9:50 AM Maik Musall wrote:
>
>
> > Am 25.09.2018 um 16:23 schrieb Andrus Adamchik :
> >
> >> "Should Cayenne by default work without prefixed accessors".
> >
> >
> > So how about this... Unless someone else steps in by then, let me
> brainstorm it with Nikita a couple of
I agree that more docs would be helpful for this. I think removing the
default cache is fine, but it should probably log a WARN message if used
without a real cache then.
On Tue, Sep 11, 2018 at 6:37 AM Andrus Adamchik
wrote:
> I've been working on Cayenne training class material lately. This
+1
1) verified checksums
2) verified signatures
3) verified archives are basically identical between platforms
4) RAT indicates no unlicensed files
5) compiled from source
6) unit tests ran successfully
On Mon, Aug 6, 2018 at 8:52 AM Nikita Timofeev
wrote:
> Hi all,
>
> Here is a second try of
I have the same test failure. If I skip the tests, the rest of the release
check completes successfully for me, so I am +1.
I'd recommend just adding an @Ignore annotation to this test so that the
rest of the tests can be run without any problems.
On Wed, Jul 18, 2018 at 9:55 AM Nikita Timofeev
I ran my checks and this release looks good. +1
On Tue, Jul 17, 2018 at 3:06 AM Nikita Timofeev
wrote:
> Thanks Andrus for catch, tried to shortcut via Mac, no luck :)
>
> Rebuild windows assemblies and committed (with new signatures) to
> https://dist.apache.org/repos/dist/dev/cayenne/4.1.M2/
Thanks Mike,
I wasn't aware of the specifics regard the review, so that is very helpful.
Are there instructions around for how to verify these things? With a
specific task list I can probably help with this more than I have before.
I would be in favor of shorter release cycles - 5 years is
at local cache
> was
> > local to that object context, but it really ends up being global. I had
> a
> > couple of Caffeine solutions in place too that did bind it closer to the
> > EC. I've since scrapped that (not sure why) and it least ties the cache
> to
> > my web
My main problem was that the docs imply that locally cached things are tied
to a single object context, giving the expectation that when the context
goes away the locally cached things go away too. This is only superficially
true -- indeed you can't access them anymore, but the objects are still
I've started using the Query Cache more in some apps and I have noticed a
problem with the way it uses memory.
BACKGROUND
Cayenne has two versions of the Query Cache - Local and Shared. The shared
cache data is available to all ObjectContexts. The Local cache data is
available only to the same
oticed this too, maybe we should change cgen templates to use
> Object type exactly as set in the model. After all it is confusing by
> itself regardless problem you mentioned.
> As for treating zero as missing PK, this can be harder as logic around
> there looks fragile to me.
>
> On F
I've found another issue with 4.1.M1 through my unit tests. If you have:
1) modeled a primary key as an ObjAttribute, like customerPK
2) modeled it as an object type, like java.lang.Long
3) are using the Cayenne-Generated (Default) PK generation strategy
Then Cayenne won't generate any PKs for
I like it!
On Tue, Sep 26, 2017 at 1:22 AM Andrus Adamchik
wrote:
> We've discussed the new website before, and Ari posted a prototype. Based
> on that we did some work on a more detailed design, which I'd liek to
> present here:
>
> 1. Home page:
default factory binding, so that the code like yours above would simply
> fail instead of giving the wrong factory:
>
>binder.bind(Key.get(MergerTokenFactory.class,
> "failoverFactory").to(DefaultMergerTokenFactory.class);
>
> In the meantime please use MergerTokenFactoryProvider
Yeah I had that same problem. Very confusing.
On Sat, Sep 23, 2017 at 10:22 AM Andrus Adamchik
wrote:
> 4.1 is also affected by CAY-2366. Also found another really minor issue -
> https://issues.apache.org/jira/browse/CAY-2367
>
> Running LinkRest under Cayenne 4.1 was a
d DbAdapter object):
>
> @Inject
> MergerTokenFactoryProvider factoryProvider;
> // ...
> MergerTokenFactory factory = factoryProvider.get(adapter);
>
> [1] https://issues.apache.org/jira/browse/CAY-2116
>
> On Wed, Sep 13, 2017 at 5:13 PM, John Huss <johnth...@gmail
your data source (via AutoAdapter or MySQLAdapter)?
>
I have custom DataSourceFactory specified in the cayenne project, but no
override of the adapter (for MySQL), so it is using AutoAdapter.
>
> On Tue, Sep 12, 2017 at 11:45 PM, John Huss <johnth...@gmail.com> wrote:
> > Also, the co
Also, the correct MergerTokenFactory for my DbAdapter is not longer
automatically detected (both for Postgres and MySQL). I had to add this to
my ServerRuntime module to fix it.
binder.bind(MergerTokenFactory.class).to(PostgresMergerTokenFactory.class);
On Thu, Aug 17, 2017 at 9:21 AM John
+1
On Sat, Aug 19, 2017 at 4:26 AM Andrus Adamchik
wrote:
> > Changing the iconography and removing the color both at the same time
> made
> > the modeler so much harder to use.
>
>
> I don't have such a strong feeling about this, but I still agree with
> Tony. I had the
I just got done upgrading several projects to use the latest from master. I
am very excited about the memory usage improvements in this version.
I wanted to relay my experience along with some of the problems I had in
case it would be helpful to others or allow this process to be smoothed
out.
+1
On Wed, Jul 26, 2017 at 6:13 AM Michael Gentry
wrote:
> +1
>
>
> On Wed, Jul 26, 2017 at 5:52 AM, Nikita Timofeev <
> ntimof...@objectstyle.com>
> wrote:
>
> > Hi all,
> >
> > I think it is time to drop support for Java 7 in 4.1.
> >
> > Java 7 has reached EOL couple
; >>>>> 12.5 vs 14.5 <<<
> >>
> >> 3. readPropertyDirectly:
> >>>>> 152 vs 248 <<<
> >>
> >> 4. writePropertyDirectly:
> >> This is map.put() vs switch(String) battle,
> >> and map def
> > and difference is that way?
> >
> > I personally was thinking the big improvement for using fields directly
> is
> > the speed improvement. I didn't think the memory consumption difference
> > would be that dramatic.
> >
> > Thanks,
> >
Thanks for commenting! See below.
On Fri, Jun 9, 2017 at 12:48 PM Andrus Adamchik <and...@objectstyle.org>
wrote:
> Ah, an exciting topic!
>
> > On Jun 9, 2017, at 5:55 PM, John Huss <johnth...@gmail.com> wrote:
> > For my test of loading 10,000 objects from ever
I did some experimenting recently to see if changes to the way data in
stored in Cayenne objects could reduce the amount of memory they consume.
I chose to use separate fields for each property instead of a HashMap
(which is what CayenneDataObject uses). The results were very affirming.
For my
I agree that the current behavior is better. However, adding a
localObjects(...) method that takes a var-args list would be helpful.
deleteObjects is already like this.
On Mon, Dec 19, 2016 at 5:01 AM Andrus Adamchik
wrote:
> We've had a concept of "persistence by
The DataMap (model) is shared by the contexts. To make them different you
need to create two different ServerRuntimes.
On Fri, Nov 18, 2016 at 3:44 AM Markus Reich
wrote:
> Hi,
>
> I have a very special requirement :-)
> We need to change the schema after logon
A pull request is preferred now.
The biggest problem with the importer that I recall was that it was
completely unaware of prototypes (ERPrototypes) so that basically made it
worthless for me. Are you having that problem? Reverse-engineering from
the database itself can work well as an
On Tue, Jan 5, 2016 at 4:35 PM Aristedes Maniatis wrote:
> On 5/01/2016 11:58pm, Michael Gentry wrote:
> > Hi,
> >
> > I'd like to start a conversation about future improvements for CM.
>
> Cool!
>
>
> > My current wish list:
> >
> > - Java Entities
> > - Class Level:
> >
I've noticed that during the PRE_UPDATE lifecycle callback, if you update a
different object the PRE_UPDATE callback is not invoked for that object
before the commit occurs. It would be preferable to have the callback
still execute before the commit.
For example,
I am using PRE_UPDATE to
I'd like to have structured data that can be inspected for particular keys,
usually attribute names. Rather than a serialized form. My use involves
setting a modification time but only if some interesting parts were changed.
For what it's worth, what Wonder has is two dictionaries, one with the
1 - 100 of 204 matches
Mail list logo