Timeline for Replacing Dynamic SQL w/ a Filtering Pipeline?
Current License: CC BY-SA 3.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 25, 2016 at 20:55 | audit | Reopen votes | |||
| Aug 25, 2016 at 20:56 | |||||
| Aug 13, 2016 at 18:05 | answer | added | JDT | timeline score: 1 | |
| Aug 13, 2016 at 12:06 | comment | added | Doc Brown | ... moreover, if the SQL creation would a Java program, you could easily unit test it (without the database). Just write tests which compares the generated queries for different parameter sets with a list of expected queries. | |
| Aug 13, 2016 at 12:01 | comment | added | Doc Brown | A dynamic SQL approach is not necessarily bad, if the creation code is well structured and maintainable. Why is the SQL creation done in a stored procedure, instead of a java function or class at the client side? Moreover, if you are going to move the place where the filtering occurs from the server to the client, your program will always need to transfer all inventory items over the network, for every query, and then might throw away lots of that data again. If that is the case, it might become a performance problem. | |
| Aug 12, 2016 at 16:58 | comment | added | Robert Harvey | What makes you say that? Oh, the edit. Well, the abbreviation isn't really necessary. Here at Stack Exchange we prefer readability over domain-specific terms, for the same reasons that you might use IIRC in a comment, but not in an actual post. | |
| Aug 12, 2016 at 16:44 | comment | added | benjamin | lol someone really doesn't like the term sproc. | |
| Aug 12, 2016 at 16:43 | comment | added | benjamin | @JDT: Inventory can be restricted such that a person in a given group may only be allowed to order a certain number of items (usually over a sliding window, say 3 items every 30 days or something). As mentioned, this sproc's only ever gotten more complicated over time, hence my question. | |
| Aug 12, 2016 at 13:35 | history | tweeted | twitter.com/StackProgrammer/status/764092961634127876 | ||
| Aug 12, 2016 at 12:48 | comment | added | JDT | I'm kind of curious, how does a stored procedure about retrieving inventory items have anything to do with how MANY somebody can order? Not seeing certain items I can understand, but that... | |
| Aug 12, 2016 at 12:13 | history | edited | Tulains Córdova | CC BY-SA 3.0 |
changed every ocurrence of 'sproc' for 'store procedure'
|
| Aug 11, 2016 at 21:22 | history | edited | benjamin | CC BY-SA 3.0 |
added 63 characters in body
|
| Aug 11, 2016 at 21:16 | history | edited | benjamin |
edited tags
|
|
| Aug 11, 2016 at 21:14 | comment | added | Robert Harvey | You could try something like Coollection. It's not Linq for Java, but it's close. | |
| Aug 11, 2016 at 21:12 | history | edited | benjamin | CC BY-SA 3.0 |
deleted 3 characters in body
|
| Aug 11, 2016 at 21:00 | review | First posts | |||
| Sep 10, 2016 at 21:13 | |||||
| Aug 11, 2016 at 20:59 | history | asked | benjamin | CC BY-SA 3.0 |