Andrew Zeneski wrote:
I cannot say exactly how much damage it causes, but since this is as far
as the framework will compile, I figured it was time for a quick patch.
If you have a better fix, please by all means check it in. Otherwise,
let's just make sure we can compile the trunk without
David E Jones wrote:
Interesting... this is worrisome as it means something isn't using the
ByteWrapper properly. Only the bytes in the ByteWrapper should be sent
to the database, not a serialized version of the object itself.
Because this issue exists we have a problem though... updating
On Oct 23, 2007, at 12:32 AM, Adam Heath wrote:
David E Jones wrote:
Interesting... this is worrisome as it means something isn't using
the
ByteWrapper properly. Only the bytes in the ByteWrapper should be
sent
to the database, not a serialized version of the object itself.
Because
David E Jones wrote:
The REAL problem, as I see it, is that what makes it into the database
is not the binary content, it is the binary content in a serialized Java
object, which is really weird. So, I'm working on code changes to get
away from that and just send the bytes over.
Well, we
[
https://issues.apache.org/jira/browse/OFBIZ-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536942
]
Jacopo Cappellato commented on OFBIZ-1243:
--
I did more research on this and I'd say that this is not a bug
David E Jones wrote:
It's an interesting idea. Maybe a better place for the isManual (or
maybe a better name is manualOnly?) flag is on the
ProductStorePromoAppl entity...
-David
David,
this is a *great* idea, thanks!
I'll immediately go for it.
Jacopo
[
https://issues.apache.org/jira/browse/OFBIZ-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Geisert updated OFBIZ-1281:
-
Attachment: new-defaultProductStoreEmail.diff
Ah, I thought PRDS_CUST_REGISTER is a new
What database error code is customized according to this message:
SQL Exception occurred on commit (Cannot commit a transactional connection:
See JDBC 2.0 Optional Package Specification section
7.1
We DBA is asking it and no have answers for it issue.
We work with a mysql database (innodb)
did a google search on
See JDBC 2.0 Optional Package Specification section 7.1
got lots of hits.
My guess is that you don't have the correct driver for the mysql your using.
Jose Diaz sent the following on 10/23/2007 9:51 AM:
What database error code is customized according to this message:
BTW this is not the good thread for this type of questions please use rather
user ML. You should have much more answers.
http://docs.ofbiz.org/display/OFBADMIN/Mailing+Lists
Jacques
De : BJ Freeman [EMAIL PROTECTED]
did a google search on
See JDBC 2.0 Optional Package Specification section
10 matches
Mail list logo
