Hi,
i'm thinking about implementing a database which keeps all former state in a
set special "Mnemento" tables. Beside the productive set of objects these
tables hold a copy of all objects with additional "from_date" and "to_date"
columns. Therefore i am able to "see" the state of the database at
The syntax is just like a normal component:
clazz.props.col_a
Oliver Geisser wrote:
Hi.
Starting with V2.1 Hibernate supports a mapping.
Is there a way to query for a "dynamic" property, e.g. one which is part
of a dynamic component?
For example:
I want to implement a class which holds dynam
Hi.
Starting with V2.1 Hibernate supports a mapping.
Is there a way to query for a "dynamic" property, e.g. one which is part
of a dynamic component?
For example:
I want to implement a class which holds dynamic properties:
class DynamicClass {
Long id;
Map props;
...
}
At deploy-time I w
My index was not zero based, it was essentially an identity column -- I
should have checked that. Switching to a map worked fine.
>>> "David Morris" <[EMAIL PROTECTED]> 11/21/2003 11:56:51 AM
>>>
While testing a mapping statement I keep getting an out of memory
error
(those don't give much informa
While testing a mapping statement I keep getting an out of memory error
(those don't give much information on what when where). Stepping through
the code in debug with Eclipse I get no error. I do get the error if I
try to step over the getListIterator(). This is a lazy list that hits
the initializ
Hi,
This is tangential to the subject, and is probably an
already-closed-or-dismissed-as-irrelevant issue, but I was wondering why I
cannot do something like:
Session.find/delete("from Class as glass where glass.id in (?), listOfIds,
Hibernate.COLLECTION); Or something like that
Also is there a
I know this request falls outside of Hibernate's function area, but it
is my pleasure of the product that drives this request. For two projects
I work on (at work and at home) I use a custom JDBC abstraction layer to
run custom searches, and Hibernate for most everything else. If the
Criteria API s
Yeah this is certainly something we need to look into.
Michael Gloegl wrote:
Hi,
as it now looks like we will get an AST-Parser for HQL (really cool), I
was thinking about if it would be nice to rework the Criteria API to have
it create an in-Memory HQL-AST. This could then be sent to the HQL-AS
Joshua Davis wrote:
I suggest we use a mock Queryable, so that we can test this stuff w/o
Hibernate. Its good TDD approach, I think.
Oh, maybe I misunderstood... do you mean something like Queryable? I was
looking at the real Queryable, and it's failry large and has many
dependencies.
Querya
Performance is irrelevant since Hibernate caches compiled queries in a
memory-sensitive cache. And I've never been a believer in the notion
that hand-written code is faster ;)
Joshua Davis wrote:
Will be interesting to see how that stuff will perform
compared to Gavins "top-of-his-head" parser
Hi,
as it now looks like we will get an AST-Parser for HQL (really cool), I
was thinking about if it would be nice to rework the Criteria API to have
it create an in-Memory HQL-AST. This could then be sent to the HQL-AST to
SQL transformator which will be needed anyways. This would remove SQL
Gene
11 matches
Mail list logo
