Hey John:
I think the validate methods are a good option. I’d be interested in knowing if
this is a roadblock everyone will eventually run into or whether it is unique
to your system. If it is something everyone will eventually run into, might be
best to go with the lowest level fix possible so
Thank you Tim and Ray,
Just moved to Mac OS 10.15.7 in development which has given me the headaches
I have installed the latest mysql 8.0.22
Java 8 (I use Java Web Start which keeps me on 8 for now)
As my production system is on mysql 5, I found I had to use
mysql-connector-java-5.1.44 which curr
I was seeing the same at one point. I believe that upgrading the jdbc
driver I was using fixed it. What version of the jdbc driver jar are you
using? I am using mysql-connector-java-8.0.19.jar.
% java --version
java 14 2020-03-17
Java(TM) SE Runtime Environment (build 14+36-1461)
Java HotSpot(T
John:
Off the top of my head these may be a couple options:
1. In your EO super class, override willInsert or awakeFromInsertion. The
former assumes you’re extending ERXGenericRecord. Not so elegant but you could
clobber every instance of a certain attribute type - with some overhead.
2. Possib
Hi again list,
My move to Catalina forced me to mysql 8. The previous version allowed NULL to
be passed to TIMESTAMP fields causing mysql to set them automatically, but the
NULL passed in the INSERT statements causes an error.
From reading around I believe they should be passed as a blank “” ra
