{"action":"opened","issue":{"url":"https://api.github.com/repos/nopSolutions/nopCommerce/issues/3193","repository_url":"https://api.github.com/repos/nopSolutions/nopCommerce","labels_url":"https://api.github.com/repos/nopSolutions/nopCommerce/issues/3193/labels{/name}","comments_url":"https://api.github.com/repos/nopSolutions/nopCommerce/issues/3193/comments","events_url":"https://api.github.com/repos/nopSolutions/nopCommerce/issues/3193/events","html_url":"https://github.com/nopSolutions/nopCommerce/issues/3193","id":345135413,"node_id":"MDU6SXNzdWUzNDUxMzU0MTM=","number":3193,"title":"Review  DB schema ","user":{"login":"picam7","id":40835299,"node_id":"MDQ6VXNlcjQwODM1Mjk5","avatar_url":"https://avatars2.githubusercontent.com/u/40835299?v=4","gravatar_id":"","url":"https://api.github.com/users/picam7","html_url":"https://github.com/picam7","followers_url":"https://api.github.com/users/picam7/followers","following_url":"https://api.github.com/users/picam7/following{/other_user}","gists_url":"https://api.github.com/users/picam7/gists{/gist_id}","starred_url":"https://api.github.com/users/picam7/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/picam7/subscriptions","organizations_url":"https://api.github.com/users/picam7/orgs","repos_url":"https://api.github.com/users/picam7/repos","events_url":"https://api.github.com/users/picam7/events{/privacy}","received_events_url":"https://api.github.com/users/picam7/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-07-27T08:23:36Z","updated_at":"2018-07-27T08:23:36Z","closed_at":null,"author_association":"NONE","body":"nopCommerce version: All versions\r\nSteps to reproduce the problem:  CALL any API Plugin.\r\n\r\nThe customer table should only be used as a customer table.\r\n\r\nIn nopcommerce ( any version ) each request to the API endpoints create a new customer.\r\nThe creation of the Guest users is caused by the default authentication in nopCommerce and we have no way to prevent it \r\n\r\nin synchronization operations, when the API is called hundreds of times, the id of the customer table increases continuously. If at the same time a customer registers himself, the ID passes (for example) from 10 to 1010 and so on...\r\n\r\nThe design choice made for the customer table causes several problems when we want to synchronize the nopcommerce database with an on-premise database.\r\n\r\nYou should use a temporary table for the SESSIONs and a customer should be INSERTED in the Customer table, under transaction, inthe order confrimation STEP. \r\n\r\nFurthermore, it should be considered the possibility of using GUID instead of Integer IDs for all tables and foreign keys, especially to facilitate the development of Mobile Apps that want to insert records in off-line mode.\r\n\r\n"}}
{"actor":{"display_login":"picam7"}}