Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB Enhancement Requests and Suggestions » View Thread |
Messages 11 to 12 of 12 total |
EDBManager SQL WIndow |
Wed, Sep 25 2013 4:06 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Steve
>I agree, that works fine in some situations and that is usually how I introduce new code. I write the SQL in a separate window and when I get it working, paste the code into the existing stored proc. But sometimes it's not easy to extract code out of a complex stored proc. And when you're pair programming with an SQL guru who says "you don't need to copy the code out, you just do it like this". The speed and skill of the SQL gurus I work with is just amazing. They can write complex SQL so quickly, and it works first time. It just goes over my head sometimes. I used to be like that with APL, less chance of RSI as well cos fewer characters to type Roy |
Mon, Sep 30 2013 3:45 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Raul,
<< As i recall Tim saying the reason for not using ; was that the procedures and triggers, etc include the ";" so it confuses the editor gutter selection parsing logic. >> ^^^^ This. The editor isn't using the engine for the parsing, so it doesn't have the ability to do contextual parsing. Elevate Web Builder is getting close to having this type of functionality (closer integration of compiler/editor), and at some point I'll be merging the two, but for now they're going to stay separate. Tim Young Elevate Software www.elevatesoft.com |
« Previous Page | Page 2 of 2 | |
Jump to Page: 1 2 |
This web page was last updated on Friday, March 29, 2024 at 03:30 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |