!      Safe Safegraphql-w-persistentRScalarTypes are the other subfield type. They are also found at object attributes. graphql-w-persistent`NestedObjects are the general object type. They are found as RootObjects or as object Subfields. graphql-w-persistent3These are objects to represent GraphQL query roots. Safe !"#$%&'()Safe *+,-./012SafeT:3456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklSafesmnopqSafers Safe tuvwxyz{|}~VHere is methods to interpret your GraphQL-SQL query and process the Persistent resultsIPS jasonsychau@live.ca  provisional Safengraphql-w-persistentAThis is the function to call to get queries from a GraphQL query.The ordered arguments are:the GraphQL query as a stringa list of tuple of String and list of String that is unique server object names and all names that are referencing then with any querya list of tuple of String and list of String that is exact same unique server object names while the list is the valid server object scalar subfields as they are spelt in the databasea list of tuple of String and list of String that is exact same unique server object names while the list is the valid server object nested object subfields as they are referenced in the next list of relationship tablesa list of tuple of String, String, and list of String that is above server object names to make an identity name, a reference name, and a list of String that is identity table, escape identity column name, reference table, arrival reference column name, and an from-to order of intermediate table triplet strings of intermediate table name, intermediate table arrival column name, and intermediate table departure column namecThe return value is a tuple of server representation objects and a list of list of sql queries. The first list is holding lists that are grouping queries from the same GraphQL query. The inner list is holding the String value sql queries. The server representation objects is later used to format database results to the GraphQL return value syntax.xHere is an example of the GraphQL schema arguments that are expected from the last five arguments. We'll use the GitHub  3https://github.com/jasonsychau/graphql-w-persistentexample: database schema to illustrate the expected arguments.The first schema argument (second argument) is a mapping to names that a server object is possibly referred to in any GraphQL query:  [(Person,[Person,"person","owner"]),(Family,[Family ,"family"]),(Genus,[Genus ,"genus"]),(Species,[Species,"species"]),(Breed,[Breed ,"breed"]),(Pet,[Pet ,"pet"]),(Taxonomy,[Taxonomy,"taxonomy"])] The second schema argument is a mapping to valid scalar subfields from every server object that is listed in the first schema argument:  [(Person,["name","gender"]),(Family ,["name"]),(Genus ,["name"]),(Species ,["name"]),(Breed ,["name"]),(Pet,["name","gender"]),(Taxonomy,["name"])] xNOTE: You should give only the intersection subfields set to parent server objects with all the children server objects.The third schema argument is a mapping to valid nested object (or entity) subfields from every server object that is listed in the first schema argument:  [(Person ,["pet"]),(Family%,["genus","species","breed","pet"]),(Genus&,["family","species","breed","pet"]),(Species$,["family","genus","breed","pet"]),(Breed&,["family","genus","species","pet"]),(Pet0,["owner","breed","species","genus","family"]),(Taxonomy ,["pet"])] xNOTE: You should give only the intersection subfields set to parent server objects with all the children server objects.NOTE: These nested object names are exact reference to the destination argument in the below relationships schema argument (the last argument).The fourth schema argument is a mapping to exact database names (it is maybe helpful to first have the database schema and copy names to this list mapping) for every listed server object in the first schema argument:  [(Person,["person"]),(Family,["family"]),(Genus ,["genus"]),(Species,["species"]),(Breed ,["breed"]),(Pet ,["pet"]),(Taxonomy*,["family","genus","species","breed"])] NOTE: This is where can you introduce type heirarchies and generalizations. The above Taxonomy server object is an example. You can see that it is an encompassing term for all the biological classifications in our database schema. The fifth schema argument is a mapping to exact database table names and fields names to link the from-object to the to-object.Within every tuple,the first String is the database table name (with type heirarchies, you make a separate tuple on every referenced database table if the to-from pair is not already mentioned as explicit pairing).The second String is the nested object subfield name that is given in the third schema argument (there is a tuple for every pairing).The third tuple value is a list that is showing the link between our identity table and referring table. The order is first identity database table name, second identity database leaving field name, third referencing database table name, fourth referencing database table arrival name, and the remainder (if identity table and referencing table are not directly linked) is a triplet of Strings that are ordered from nearest to identity table to closer to referencing table. The triplets are intermediate database table name, intermediate database arrival field, and intermediate database exiting field. Here is an illustration:  4 -- Person [("person","pet",["person","id","pet","id","pet_ownership","owner_id","animal_id"]), ("person","breed",["person","id","breed","id","pet_ownership","owner_id","animal_id","pet","id","id","pet_type","pet_id","breed_id"]), ("person","species",["person","id","species","id","pet_ownership","owner_id","animal_id","pet","id","id","pet_type","pet_id","breed_id","breed","id","species_id"]), ("person","genus",["person","id","genus","id","pet_ownership","owner_id","animal_id","pet","id","id","pet_type","pet_id","breed_id","breed","id","species_id","species","id","genus_id"]), ("person","family",["person","id","family","id","pet_ownership","owner_id","animal_id","pet","id","id","pet_type","pet_id","breed_id","breed","id","species_id","species","id","genus_id","genus","id","family_id"]), -- Family ("family","pet",["family","id","pet","id","genus","family_id","id","species","genus_id","id","breed","species_id","id","pet_type","breed_id","pet_id"]), ("family","genus",["family","id","genus","family_id"]), ("family","species",["family","id","species","genus_id","genus","family_id","id"]), ("family","breed",["family","id","breed","species_id","genus","family_id","id","species","genus_id","id"]), -- Genus ("genus","pet",["genus","id","pet","id","species","genus_id","id","breed","species_id","id","pet_type","breed_id","pet_id"]), ("genus","family",["genus","family_id","family","id"]), ("genus","species",["genus","id","species","genus_id"]), ("genus","breed",["genus","id","breed","species_id","species","genus_id","id"]), -- Species ("species","pet",["species","id","pet","id","breed","species_id","id","pet_type","breed_id","pet_id"]), ("species","breed",["species","id","breed","species_id"]), ("species","genus",["species","genus_id","genus","id"]), ("species","family",["species","id","family","genus_id","genus","species_id","id"]), -- Breed ("breed","pet",["breed","id","pet","id","pet_type","breed_id","pet_id"]), ("breed","species",["breed","species_id","species","id"]), ("breed","genus",["breed","species_id","genus","id","species","id","genus_id"]), ("breed","family",["breed","species_id","family","id","species","id","genus_id","genus","id","family_id"]), -- Pet ("pet","owner",["pet","id","person","id","pet_ownership","animal_id","owner_id"]), ("pet","breed",["pet","id","breed","id","pet_type","pet_id","breed_id"]), ("pet","species",["pet","id","species","id","pet_type","pet_id","breed_id","breed","id","species_id"]), ("pet","genus",["pet","id","genus","id","pet_type","pet_id","breed_id","breed","id","genus_id"]), ("pet","family",["pet","id","family","id","pet_type","pet_id","breed_id","breed","id","genus_id","genus","id","family_id"])] #To implement server type heirarchy:'add new tuple to first schema argument,`add new tuple to second schema argument (where list is the intersection fields on all children),_add new tuple to third schema argument (where list is the intersection fields on all children),Yand add new tuple to fourth schema argument (where list is all children database tables).You should not need more cases within fifth schema argument, but you may find a child database table ane and third schema argument list elements pair that is not included.8Then, you will need to include this, or error is thrown.VAs a final note, we turn our attention to what is posted on the official GraphQL docs: "In contrast, GraphQL only returns the data that's explicitly requested, so new capabilities can be added via new types and new fields on those types without creating a breaking change. This has lead to a common practice of always avoiding breaking changes and serving a versionless API." - /https://graphql.github.io/learn/best-practices/With respect to that, you should be sure to be explicit with your here representation on your data schema. You should give as much detail as possisble (sorry for the bad pun), and you should make adjustments when they are needed to evolve your server with your desired schema. cWhen an error is encountered, an uncaught exception is thrown. Exceptions thrown by the module are: MSyntaxException (when there is a problem with the given GraphQL query syntax)GParseFragmentException (when there is a problem with a Fragment syntax)2EmptyQueryException (when the query is left blank)InvalidObjectException (when there is problem in nested object syntax, an object is not recognized, or server data is misinterpreted)}InvalidObjectSubFieldException (when a subfield is requested from nested object that is not having ownership of the subfield)nInvalidScalarException (when there is syntax error in listing scalar fields, or server data is misinterpreted){NullArgumentException (when a transformation is set but no argument is given though we do not yet support transformations) CreatingSqlQueryObjectFieldsException (when there are too many nested object subfields than nested objects to hold them or when there is a problem with the aligning of server object relationship argument - that's the fifth schema argument)RelationshipConfigurationException (when the relationship schema fifth arugment is incorrect number of String values or when an unrecognized pairing is found)graphql-w-persistentYThis is the function to call after casting PersistValues to Text from processQueryString.The ordered arguments are:&all the data that is cast to Text typeSan unmodified copy of the RootObject list that is returned from processQueryString.CThe return result is a string to resemble the GraphQL return value.8Making the first argument is demonstrated in the GitHub  3https://github.com/jasonsychau/graphql-w-persistentexample.hCurrent implementation is to cast all values to Text since arbitrary columns data types are not infered.\When an error is encountered, an uncaught exception is thrown. The exceptions thrown are of:;InvalidObjectException (when server data is misinterpreted);InvalidScalarException (when server data is misinterpreted)qEOFDataProcessingException (when the given data is shorter than expected in reference to the given serve objects)aInvalidArgumentException (when there is an internal argument error - you should not observe this)graphql-w-persistent!GraphQL query argument as String.graphql-w-persistent4Server object name to list of query reference names.graphql-w-persistentkServer object name to list of valid scalar subfields (which are exactly named after database column names).graphql-w-persistentServer object name to list of valid nested object subfields (which are exactly named after the from and to strings within the last function argument).graphql-w-persistent_Server object name to list of database table names (which are exact references to table names).graphql-w-persistentServer object name to list of from-to-and intermediate triplet strings as described above to identify all GraphQL relationships with database sequences.graphql-w-persistentXThe return value is one tuple with server objects and list of grouped sql query strings.graphql-w-persistentdatabase query return value as casted to only Text data types and with no other alterations (a list of GraphQL-grouped results list of SQL query results list of data row lists)graphql-w-persistentUunmodified server objects that was given by the previous processQueryString function.graphql-w-persistentRThe return value is a string type to describe the GraphQL-organized return values.        !"#$%&'()*+,-./0123456789:;;<=>>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxy z { | } ~  3graphql-w-persistent-0.1.0.4-D0FEAzF66o73VRfMdE7upTGraphQLModel.ServerExceptionsModel.ServerObjectTypes(Components.ObjectHandlers.ObjectsHandler*Components.QueryComposers.SQLQueryComposerComponents.Parsers.QueryParser/Components.ObjectHandlers.ServerObjectValidator GraphQLHelper1Components.DataProcessors.PersistentDataProcessorNameArgumentTransformation ScalarTypeField SubFields SubSelection ServerObjectAlias NestedObject RootObject RootObjectsprocessQueryStringprocessPersistentDataQueryException"RelationshipConfigurationExceptionInvalidArgumentExceptionEOFDataProcessingException%CreatingSqlQueryObjectFieldsExceptionNullArgumentExceptionInvalidScalarExceptionInvalidObjectSubFieldExceptionInvalidObjectExceptionEmptyQueryExceptionParseFragmentExceptionSyntaxExceptionreadServerObjectisValidServerObjectScalarField$isValidServerObjectNestedObjectFieldtranslateServerObjectToDBNamegetDBObjectRelationships getScalarNamegetScalarArgumentgetTransformation getObjectNamegetServerObject getSubFieldswithSubSelectiongetSubSelectionFieldgetSubSelectionArgumentmakeSqlQueriesmakeSqlQuerySetmakeSqlTablePhraseaddSqlQueryFieldsremoveLastChar getNewTablesgetNewTablesHelpermakeTransitionscompleteTransitionReplacerswitchtargetFragment replacement targetObjectname processStringremoveCommentsremoveCommentsHelperremoveLinebreaks validateQueryvalidateBracketLocationQuery"validateBracketLocationQueryHelpervalidateNoEmptyBracketsvalidateNoEmptyBracketsHelperparseStringToObjectsgetQueryAndFragmentsgetQueryAndFragmentsHelperparseFragmentsparseFragmentsHelpercreateFragmentcreateFragmentHelperisValidFragmentNameCharisValidIdentifierCharsubstituteFragmentssubstituteFragmentsHelpergetNestedObject findFragment splitSubjectsubstituteHelper isMatchingcomposeObjectscomposeObjectsHelperseparateRootObjectsseparateRootObjectsHelpercreateNestedObjectcreateNestedObjectHelperparseServerObject parseAlias parseNameparseSubSelectionparseSubFieldsparseSubFieldsHelperremoveLeadingSpacesremoveSubSelectiongetSubSelection extractLevelextractLevelHelper removeLevelremoveLevelHelper removeSpacescreateScalarTypeparseTransformation parseArgumentremoveSideSpacescheckObjectsAttributeshasValidAttributesisValidSubSelectionisValidSubFieldsisValidSubField checkString checkObjectsprocessReturnedValuesprocessReturnedValueprocessSubFieldscomposeGraphQlRowfetchGraphQlRow removeDataRowgetScalarFieldLabelgetNestedObjectFieldLabelpullNDataColumnscountNestedObjectQueriedFields!countNestedObjectQueriedSubFieldsremoveNDataColumns