I didn't got answers from that important question :
let's imagine we'll have to do it. Let's be clear here : we're considering
option to add that to OpenJPA and share it back as Open source of course.
How will we describe it in OpenJPA ?
Should we have some technical annotation like @NativeTrigg
> some technical annotation like @NativeTrigger or should we have higher
> level annotation like @Audit ?
I prefer @Audit to @NativeTrigger.
In fact I see two specifications
a) one on the persistent domain entity as an annotation
@Entity
@Auditable
public class Customer {
I like @Auditable because it's easy to switch on auditing of specific
entities or entity hierarchies. But the property would allow for
auditability globally to be turned on or off. Personally I would favour
also adding a property like :
-
Pinaki
--
View this message in context:
http://
Actually OpenJPA plug-in property takes care such that one can use mneomonics
rather than implementation class name. Also the plug-in can configure the
concrete implementation if it has bean style methods
So instead of
http://openjpa.208410.n2.nabble.com/JPA-for-portable-database-management-tp
> Does OpenJPA assume that DB collation is always case insensitive?
Many properties of database can be configured using following syntax.
Each known database has a corresponding mnemonics such as 'sqlserver' --
which is realized by openjpa.jdbc.SQLServerDictionary. The properties of
t
Hi,
When I try to insert a XML object into a XMLType column in Oracle with
more than 4000 characters, I get the following exception.
ORA-01461: can bind a LONG value only for insert into a LONG column
Is there anyway we can work around that? My mapping works fine when
the XML can be serialized wi
Hello,
OpenJPA advertises itself as an expandable framework and provides @Strategy
(and undocumented) @ElementStrategy annotations to create custom java<->SQL
mappings.
I would like to create support for already existing JDBC4 standard mapping
of primitive arrays in i.e. Postgres:
java double[]
Hi Nino,
Roughly speaking, the idea is that you implement some database-specific
listener. The listener is invoked when the data you are interested in changes.
Until the listener is invoked, you can use data from the cache. When the
listener is invoked, you refresh the entities or execute your
Hi Christopher,
As it turns out, I don't think this problem is the same as OPENJPA-1259.
There is special code in the PostgresDictionary that treats sequences
suffixed with "_SEQ" as system managed sequences. The comment in
PostgresDictionary.isSystemSequence reads:
// filter out generat
Jersey,
You are right. I changed the sequenceName to xxx and it works...
Thx for help :)
Am 08.06.2010 23:17 schrieb "Jeremy Bauer" :
Hi Christopher,
As it turns out, I don't think this problem is the same as OPENJPA-1259.
There is special code in the PostgresDictionary that treats sequences
s
I'd appreciate some comments about what I could be doing wrong. I am using
build time enhancement.
Using openjpa v1.2.1.
maven property set to...
openjpa.jdbc.SynchronizeMappings = "buildSchema(ForeignKeys=true)"
http://java.sun.com/xml/ns/persistence"; version="1.0">
org.apache.openjpa
11 matches
Mail list logo
