Denis, I think I know why you are getting such error.
You are using DEMO, and demo is running INSIDE web-agent and web-agent built on ignite-1.7 branch that does not have DML support. We will prepare updated version of web-agent based on ignite-1.8 and it will support DML in DEMO. Meanwhile you could start real cluster >= ignite-1.8 and connect to that cluster with web agent and execute DML. On Fri, Feb 10, 2017 at 2:18 AM, Denis Magda <dma...@apache.org> wrote: > Alex, > > I couldn’t execute DML queries from Web Console. Looks like something was > broken if you say it worked before. > > Try to run the demo mode and execute query like this > > UPDATE car set parkingid = 20 where id = 12 > > You will get this error. > > Error: Unsupported query: UPDATE car set parkingid = 20 where id = 12 > > I’ll highly appreciate if you debug and fix the issue by the time of my > webinar (Feb 15th). > > — > Denis > > > > On Feb 9, 2017, at 12:16 AM, Alexey Kuznetsov <akuznet...@apache.org> > wrote: > > > > Denis, thanks for your feedback. > > > > I will take a look and make Web Console more user friendly. > > > > Dima, > > > > DML is already supported by Web Console because it is SqlFieldsQuery and > > there no difference from "Select * from Person" and "Delete from person > > where ID > 500". > > > > If DDL will be also implemented as SqlFieldsQuery - it will be supported > by > > Web Console out of the box without changing a single line of code. > > > > I will investigate this once DDL will be ready. As far as see we will > need > > (at least) support custom syntax for things like (create cache(....)). > > > > > > On Thu, Feb 9, 2017 at 7:38 AM, Dmitriy Setrakyan <dsetrak...@apache.org > > > > wrote: > > > >> Apart from all the issues listed by Denis, I would say that DML and the > >> upcoming DDL should be enabled in the Web Console. Otherwise SQL support > >> just seems incomplete. > >> > >> Is this difficult to add? > >> > >> D. > >> > >> On Wed, Feb 8, 2017 at 3:48 PM, Denis Magda <dma...@apache.org> wrote: > >> > >>> Alex K., > >>> > >>> As a part of preparations to the upcoming Web Console related webinar I > >>> faced with a couple usability issues. > >>> > >>> *DML* > >>> Not supported at the moment. I’ve created a ticket and propose > to > >>> release it in 1.9 (https://issues.apache.org/jira/browse/IGNITE-4674 < > >>> https://issues.apache.org/jira/browse/IGNITE-4674>). Will you be able > to > >>> do this? > >>> > >>> *Configuration tab.* > >>> If several models created or imported from a database it’s unclear how > to > >>> switch from one to another on *Model* page in order to see or alter a > >>> configuration for a specific model. Presently, all the model names are > in > >>> red and a selected one is just a bit more saturated. This is > >>> indistinguishable. > >>> If I remove a mode the cache the mode belonged to will be left > untouched. > >>> It might lead to issues in runtime when generated classes and > >>> configurations are used. I would remove a cache as well if the cache > was > >>> created automatically during the schema importing process. > >>> Let’s say I have 10 caches and I wish to change a parameter like > backups > >>> to 2 for all of them. Presently I need to click on every cache > adjusting > >>> the parameter 10 times. Let’s simplify this “batch” update. Viktoria, > >> your > >>> thoughts are highly welcomed here. > >>> During the schema importing I saw the opportunity to choose a specific > >>> cache template. How can I create a template on “cache configurations” > >> page? > >>> Summary pages provides artifacts for the servers and clients. Please > put > >>> “help” icon to the left of “Client” and “Server” explaining what is the > >>> server and what is the client. > >>> > >>> *Project Generated by Web Console* > >>> Project’s README is incomplete. Please provide details and description > >> for > >>> every artifacts (source code, configuration files) that are in the > >> bundle. > >>> For instance, LoadCache class which is not covered there. > >>> Project’s README claims that all the configuration is in “config” dir > >>> while in fact all configuration files are under “resources/META-INF”. > >>> > >>> *Mac OS Specific* > >>> It’s know that on Mac OS the project is downloaded as “Uknown” file. > >>> However, the warning that states this is hard to notice. Viktoria, > please > >>> take a look at this issue as well. > >>> > >>> > >>> — > >>> Denis > >> > > > > > > > > -- > > Alexey Kuznetsov > > -- Alexey Kuznetsov
