Agreed, thats the best way how NOT to do it :D
Am 13.08.19, 10:15 schrieb "Xiangdong Huang" <[email protected]>:
Hi,
Either is fine.
The only thing is that I want to get rid of checking the error message
content....
Best,
-----------------------------------
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Julian Feinauer <[email protected]> 于2019年8月13日周二 下午4:12写道：
> Hi all,
>
> what one could also use is some "ResponseEnum" which could be hosted in an
> error code, perhaps?
> But, generally I agree with Tian.
>
> Julian
>
> Am 13.08.19, 10:07 schrieb "江天" <[email protected]>:
>
> Well, I prefer to define new Exception classes over ugly error codes,
> which better utilize OOP.
>
> Tian Jiang
>
> > 在 2019年8月13日，下午4:00，Xiangdong Huang <[email protected]> 写道：
> >
> > Hi,
> >
> > When using IoTDB-JDBC to operate data, I realize that it is not
> convenient
> > without error codes ....
> >
> > The typical application is register a new time series automatically
> if the
> > received data belongs to a not existed time series.. Now, I have to
> check
> > the error message to judge whether the keyword "exist" exists...
> >
> > I list 4 useful error codes according to my experience of using
> IoTDB, see
> > https://issues.apache.org/jira/browse/IOTDB-161
> >
> > It is an easy task comparing to other issues. Knowing how to use
> Thrift
> > will help to finish the feature.
> >
> > Best,
> > -----------------------------------
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> > 黄向东
> > 清华大学 软件学院
>
>
>
>
>
