Generating rows from C# without extractor about usql HOT 4 CLOSED

Amer, For generating constant rows: The simpler approach would be to leverage SELECT … VALUES https://msdn.microsoft.com/en-us/library/azure/mt621292.aspx For generating dynamic rows: UDO(s), such as the extractor are plenty powerful enough for that scenario. Hope that helps Ed From: Amer [mailto:[email protected]] Sent: Wednesday, December 14, 2016 4:57 PM To: Azure/usql <[email protected]> Cc: Subscribed <[email protected]> Subject: [Azure/usql] Generating rows from C# without extractor (#62) Hello all. I was trying to create a for loop, or even a for loop within a for loop, I found it rather hard in SQL language, so I decided to do it in C#. The only problem was, I didn't know how to produce results back to USQL. Right now I am using extractor to do the job @loop = EXTRACT i int FROM "" USING new ForLoopExtractor(0, 10); public class ForLoopExtractor : IExtractor { int from, to; public ForLoopExtractor(int from, int to) { this.from = from; this.to = to; } public override IEnumerable<IRow> Extract(IUnstructuredReader input, IUpdatableRow output) { for (int i=this.from; i<this.to; i++) { output.Set<int>(0, i); yield return output.AsReadOnly(); } } } Is there a more convenient way of doing this ? And also, do you plan on improving language itself to allow this ? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fusql%2Fissues%2F62&data=02%7C01%7Cedtriou%40microsoft.com%7Cb360eb896e574d07965608d424853ce6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636173602050013847&sdata=kZsQRXDYLJr831BYc2YfrcuRi1yP1ofQ61OqQEekNvM%3D&reserved=0>, or mute the thread<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANh3IZw6hJsOgg7tNuig51RI6MEdQAkoks5rIJBKgaJpZM4LNmIA&data=02%7C01%7Cedtriou%40microsoft.com%7Cb360eb896e574d07965608d424853ce6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636173602050013847&sdata=2YhbdpZ%2FtSiG5%2FvVYQR9OmbfPvSyPd1egu9tR%2Bx8mWk%3D&reserved=0>.

Ø For example, using extractor requires a file in system, and it gets opened, wasting some of resources Extractor is just one of the (6) UDO(s). (4) of the UDO(s) operate exclusively on rowsets (not files). For example: 1. Use SELECT … VALUES to get at least a 1 row rowset. 2. Followed by CROSS APPLY of a custom applier (ie: USING <your applier UDO>) That will allow you to explode that row into N. Your applier can be a data generator. Hope that helps Ed From: Amer [mailto:[email protected]] Sent: Thursday, December 15, 2016 4:08 AM To: Azure/usql <[email protected]> Cc: Ed Triou <[email protected]>; Comment <[email protected]> Subject: Re: [Azure/usql] Generating rows from C# without extractor (#62) Yes, there are pros and cons of each possibility, but none of them is perfect. For example, using extractor requires a file in system, and it gets opened, wasting some of resources. Using UDO is only applicable where I already have a lot of rows and then process them, please correct me if I am wrong here (I actually want to produce rows out of nothing). As of now, the best solution is to generate range of numbers using extractor. — You are receiving this because you commented. Reply to this email directly, view it on GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fusql%2Fissues%2F62%23issuecomment-267312722&data=02%7C01%7Cedtriou%40microsoft.com%7C32b2183fc8534dfb46bf08d424e30ba6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636174004948119814&sdata=WQoRPtq9S0RbzlP25NqlJLUYLro8bmAYRs2ujtNIj08%3D&reserved=0>, or mute the thread<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANh3IV1liGYEU8rLvNAH8wxSvkZ_cAHMks5rIS2sgaJpZM4LNmIA&data=02%7C01%7Cedtriou%40microsoft.com%7C32b2183fc8534dfb46bf08d424e30ba6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636174004948119814&sdata=LOvFaYcU8US7lnVw98ngT18QWxOkZa%2B8vrwMS3AMA44%3D&reserved=0>.