Timeline for Materializing any ADODB Query
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 29, 2018 at 2:51 | history | edited | Jamal | CC BY-SA 4.0 |
added 61 characters in body
|
| Oct 29, 2018 at 2:50 | history | notice removed | Jamal | ||
| Oct 18, 2018 at 4:15 | history | edited | Allen Mattson | CC BY-SA 4.0 |
Added code to retrieve a disconnected recordset
|
| Oct 16, 2018 at 20:50 | comment | added | Vogel612 | I agree with Mathieu here. As it stands this is not really an answer and more of a clarifying comment. If you could expand a bit on the point you're making and change the tone of the text to something more "answer"-y, that'd be appreciated. If you prefer to keep it like this, I can convert this to a comment for you. Just give me a heads up. Thanks! | |
| Oct 16, 2018 at 20:49 | history | notice added | Vogel612 | Needs detailed answers | |
| Oct 16, 2018 at 20:41 | comment | added | Mathieu Guindon | That said this looks more like a comment than an answer IMO. | |
| Oct 16, 2018 at 20:40 | comment | added | Mathieu Guindon |
Disconnected recordset is a very good point - if I wrote this today I'd scrap the SqlResult wrapper and return a disconnected recordset instead. The methods that take a connections parameter don't own it though, and thus shouldn't close it - they exist so that the code that owns the connection can initiate a transaction and run multiple commands before committing or rolling back.
|
|
| Oct 16, 2018 at 20:38 | history | answered | Allen Mattson | CC BY-SA 4.0 |