Is there a way to trace the generated SQL for stored procedures? I know how to do it for the entity/typedviews but I'm not seeing it for the stored procedures (Retrieval/ActionProcedures).

Tracing to the proc calls wasn't added as they won't add much of a value, simply because all you can trace is which proc is called and which parameters are passed which is right there in your code: all other logic inside the proc isn't traced of course, you have to use the tools provided by the rdbms for that. Only Dynamicaly built queries are thrown into the trace.

The advantage is having them in the same place. Yes, I can get it via Profiler. Yes, I can get the variables from my code but that's not exactly the same thing.

I'd put this in as a request if it's not a hard thing to add.

See this thread I started some time back about this:

http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=6959

That is the last I heard of it. I created my own template extensions/overrides to add this behavior. I would be happy to share if you are interested.

Basically, the templates are modified versions the shipping templates to add the tracing information for the stored procs. Pretty basic stuff.

Just a question: we have had the 2.5 feature discussion forum for a while and what I then wonder is... why do these requests pop up AFTER the beta is released? It's better to suggest features before development actually ended.

there will be a moment were even a change which takes just a single line of code won't make it into v2.5 and that moment appears really quickly now. Adding this will probably take 2-3 hours to add/test etc. and it's a nice thing to have in the framework. It's just that all these last-minute requests should have been requested earlier on. We have rejected some features for v2.5 because there was no time. Squeezing these last minute requests in is unfair to the people who have rejected these features. And I hate to dissapoint people who requested features.

The tracers in llblgen pro are mainly there to give insight in what's going on behind the scenes as a single call to a fetch method for example can spawn a lot of activity and a developer likely wants to have insight. A call to a proc is just that, a call to a proc. You call the proc, the proc gets called. There's not much more to tell really. That's why there aren't tracers on the proc calls.

I'll log your request into our issue tracker, I'm not sure if it will make v2.5.

Hey! No fair Otis....I DID request this back in July 2006....see link above.

WayneBrantley wrote:

Hey! No fair Otis....I DID request this back in July 2006....see link above.

heh, ok fair is fair. You did. I didn't put it onto our todo list then I guess. We migrated our todo list (made in ToDoList.exe ) to Gemini some time ago, but it doesn't appear in the list of items still in gemini.

So, as a reward for me and a punishment for you, does that mean it might make the 2.5 version?

WayneBrantley wrote:

So, as a reward for me and a punishment for you, does that mean it might make the 2.5 version?

It might, but likely not.