go to post Evgeny Shvarov · Jan 21 I see. And in my case some sets of parameters cause an anomaly, and it is not very effective to investigate it one-by-one
go to post Evgeny Shvarov · Jan 21 Thank you, @Vitaliy Serdtsev ! If enabled auditing gives the ability to see parameters, or the ability to copy/paste into SQL query tool a ready/made sql query that has been running in the system?
go to post Evgeny Shvarov · Jan 20 Thanks @David Hockenbroch ! Introduced an idea to get such a history as a system feature.
go to post Evgeny Shvarov · Jan 20 Thank you, @Robert Cemper ! Looks... complicated(?) to get an SQL query that causes anomalies?
go to post Evgeny Shvarov · Jan 19 Thank you, @Yuri Marx @Robert Cemper ! Works for me as well - my issue was that JSON.Adapter is case sensitive. if payload comes as: { "strprop": "string", "BoolProp": true } error fires (very unreadable). I thought that reason is the boolean value, but turned out it is property naming issue - should 100% match either name in a class description, or special JSON property name clause.
go to post Evgeny Shvarov · Jan 9 Thanks @Enrico Parisi ! Yes, sometimes 3641144 could be enough to store a file.
go to post Evgeny Shvarov · Jan 9 Faced the same issue. What is the size limitation on working with streams in DynamicObjects/JSON? 1MB?
go to post Evgeny Shvarov · Jan 8 This is how our ^%REST service is organized, that consumes OpenAPI spec (unfortunately not the latest one, but still workable 2.0) and generates package.spec.cls with map , package.disp.cls with dispatch and params handling and package.impl.cls with business logic implementation stubs. But what ^%REST doesn't provide - it doesn't generate unit-tests to make sure that all the impl.cls methods and dispatch methods work as expected. @David.Hockenbroch's article here is very focused exactly on this gap, thank you, Dave.
go to post Evgeny Shvarov · Jan 7 I'm still curious what does [identity] do here? property id as %Library.BigInt [ identity ]; is it only for "Object" access and not for SQL?
go to post Evgeny Shvarov · Jan 6 Ah, I see - VALUES (saleId,companyId,productId,saleDate,saleAmountUSD) Impressive indeed.
go to post Evgeny Shvarov · Jan 6 I'm curious how and if the approach work if the id name in csv is diffent of "id", e.g.."CompanyId"?
go to post Evgeny Shvarov · Jan 6 Wow. Thanks @Vitaliy Serdtsev ! This is impressive. So if I understand properly, LOAD DATA guesses somehow that id is the idkey and primarykey here? &sql(LOAD DATA FROM FILE 'C:\data\companies.csv' INTO dc_onetomany.companies(id,name,industry,description,website) USING {"from":{"file":{"header":true}}}) if AllowIdentityInsert =1?
go to post Evgeny Shvarov · Jan 6 Thanks @Dan Pasco ! So this $system.SQL.SetIdentityInsert(1) is a system-wide setting, right? It looks like there is an option to have it as a parameter for a class as well, like @Vitaliy Serdtsev shared above
go to post Evgeny Shvarov · Jan 5 Thanks Dan! I’m having these property in my class that allows inserting ID values via SQL: Parameter ALLOWIDENTITYINSERT = 1; is it what you are talking about?
