I assume that you are referring to (from sample project)
public static Person findPersonNamed(String firstName, String lastName)
{
Operation findByFirstNameAndLastName =
PersonFinder.firstName().eq(firstName)
.and(PersonFinder.lastName().eq(lastName));
return P
Hi guys,
there is an interesting project open sourced by Goldman Sachs:
https://github.com/goldmansachs/reladomo
It is a basically a Java ORM with some pretty unique features and the Query
DSL is in some ways similar to what we are using in Apache Polygene :
Person.createPerson("Taro", "Tanaka"
Stan,
yes it has struck me, and I think the answer is that indexing would then
become an issue of figuring what indexes to create in SQL. Yet to be
explored, but probably possible.
On Mon, May 8, 2017 at 9:23 PM, Stanislav Muhametsin <
stanislav.muhamet...@zest.mail.kapsi.fi> wrote:
> I agree wit
I agree with JJ here, but SQL-leads-Polygene approach is extremely hard
to do, considering that creating SQL indexing store to fully support all
stuff that Polygene query engine does is quite demanding already.
But I'm not saying it is impossible - hardly anything is. :)
And it's good that Nicla
Ok, see your point. So what you are saying now is that the first step would
be a Polygene model that would lead/specify the SQL model in a more SQL-ish
way.
That means a more natural/classical SQL schema will be generated - unlike
the key/value approach that is implemented now.
I personally would
What I mean is that this starts with a Polygene model and it will create
SQL tables.
Why not the other way around?
Well, you will immediately descend into the rabbit hole where Hibernate is.
With incomprehensibly complex mappings of tables to arbitrary sections of
code, simply not robust enough to
Hi Niclas,
thank you for taking over the ORM topic. We definitely require a
'generally' accepted approach how to deal with persistence !
'NOTE, this is only for "Java Model drives SQL model", but in an
enterprise-friendly way.'
I;m a bit confused with the above expression. From my understanding
Thanks for the views, and Slick seems to be (correct me if I am wrong) the
equivalent of JOOQ in Java. I would even argue that Slick is more "masking
it with another custom language" than JOOQ is trying to do;
Result baseEntityResult = dsl
.select()
.from( entitiesTable )
.where( ident
Hi Niclas,
I was tired of Hibernate too :-) ...
I think that your proposal looks very interesting, an approach more
related to code to me looks better (and more Java oriented) than many
current products ... but an hard point could be to find a way to let
developers write SQL code if/when needed, i
Gang,
I have gotten overly angry with Hibernate on $dayjob, and decided to take a
look at what a ORM-ish implementation in Polygene would look like. And it
was easier than I expected, so...
Pretty simple,
0. One "types table" that keep tracks of all types. Content of this is
probably fully cache
10 matches
Mail list logo
