Re: SFieldBlob convenience constructors

 Hi

You are correct, the first one is unnecessary.

Most of the time, a maximumSize is unnecessary for a blob - it exists, but generally you don't bother checking because
it's pretty unlikely that you'd ever hit it.

Regards, Noel

Franck Routier wrote:
>  
>
> Hi,
>
> actualy the first does exist (it is even the only constructor
> available) :
>
> public SFieldBlob(SRecordMeta meta, String columnName, int maxSize,
> SFieldFlags... pvals) {
> super(meta, columnName, pvals);
> setMaxSize(maxSize);
> }
>
> As for the second one, it means you can have a SFieldBlob without a max
> size. I don't use blobs myself, so I don't really know if this makes
> sense...
>
> Franck
>
> Le mercredi 30 juin 2010 à 16:00 +0200, Noel Grandin a écrit :
> >
> > Hi
> >
> > For convenience and symmetry with the other types, SFieldBlob needs
> > constructors that look like:
> >
> > public SFieldBlob(SRecordMeta meta, String columnName, int
> > maxSize)
> >
> > public SFieldBlob(SRecordMeta meta, String columnName)
> >
> >
> > Thanks,
> > Noel Grandin
> >
> >
> >
> >
> >
> >
> > __________________________________________________________
> > Disclaimer: http://www.peralex.com/disclaimer.html
> >
> >
> >
> >
> >
>
> 

Disclaimer: http://www.peralex.com/disclaimer.html