Don't remember what was the thinking around the time we wrote about the Modeler
support here. The way things are going now (with DI and stuff), our direction
is to move extensions and runtime configs from the modeler and into the custom
DI code as much as possible. So I will probably remove this
Hi,
I just realized that while I wrote this I tried to find some info on
extended types (http://cayenne.apache.org/doc30/extended-types.html).
Maybe it would be good idea to include a short example how to implement
one or at least a put note pointing user to existing types for
inspiration in
Hi,
here's the relevant code:
public class Inet4AddressType implements ExtendedType {
@Override
public String getClassName() {
return Inet4Address.class.getName();
}
@Override
public void setJdbcObject(PreparedStatement statement, Object
value, int pos, int type, i
Hi Marek,
If you don't mind sharing, I'm sure many would like to see it.
Thanks,
mrg
On Thu, Feb 10, 2011 at 5:08 PM, Marek Šabo wrote:
> Hi Michael,
>
> I fooled around a little bit and settled down with extended type
> implementation for Inet4Address. Should anyone want to see the code I ca
Hi Michael,
I fooled around a little bit and settled down with extended type
implementation for Inet4Address. Should anyone want to see the code I
can post it.
Regards,
marek
On 02/09/2011 03:30 PM, Michael Gentry wrote:
Hi Marek,
I'd probably just wrap it in utility methods, but I tend t
Hi Marek,
I'd probably just wrap it in utility methods, but I tend to take the
simple way out. Like Andrus, I'd be curious to know if you find a
different way.
Thanks,
mrg
On Mon, Feb 7, 2011 at 2:41 PM, Marek Šabo wrote:
> Hi,
>
> I would like to ask for advice, what would be a good way to
I can't predict the outcome, but certainly worth trying and reporting back the
result.
Andrus
On Feb 7, 2011, at 2:41 PM, Marek Šabo wrote:
> Hi,
>
> I would like to ask for advice, what would be a good way to get outcome of
> (my)sql functions in cayenne. Is there any other way than calling
