Hello! The best approach is to use .setIndexedTypes() instead of setQueryEntities(), and annotate complex types in question with @QuerySqlField. This way you can then pour those types into cache and it will work transparently.
Regards, -- Ilya Kasnacheev пт, 15 мар. 2019 г. в 18:28, Mike Needham <[email protected]>: > Perfect, now the next question is how would you do this for a more complex > object/table? Either one defined in a separate object or via SQL DDL? > > On Fri, Mar 15, 2019 at 9:05 AM Ilya Kasnacheev <[email protected]> > wrote: > >> Hello! >> >> You will have to specify schema name (or cache name?) in ALLCAPS when >> creating cache. >> >> Regards, >> -- >> Ilya Kasnacheev >> >> >> пт, 15 мар. 2019 г. в 16:45, Mike Needham <[email protected]>: >> >>> I see. did not have the "person" for the schema. Is there a way to not >>> have the quotes around that? >>> >>> On Fri, Mar 15, 2019 at 7:59 AM ilya.kasnacheev < >>> [email protected]> wrote: >>> >>>> Hello! >>>> >>>> Definitely works for me in DBeaver with this exact code: >>>> >>>> < >>>> http://apache-ignite-users.70518.x6.nabble.com/file/t1312/dbeaver-tables.png> >>>> >>>> >>>> Some of DBeaver's introspection does not work but statements are solid. >>>> >>>> Regards, >>>> >>>> >>>> >>>> -- >>>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >>>> >>> >>> >>> -- >>> *Some days it just not worth chewing through the restraints* >>> >> > > -- > *Some days it just not worth chewing through the restraints* >
