Samuel Nitsche comments

Results 68 comments of


                                            Samuel Nitsche

Install utPLSQL into one database but use from another one

Hey Cecilia I can share my (limited) opinion on your situation: > Our question is whether this type of installation and use can cause any problems in the operation of...

Documentation: Make clear that beforeeach and aftereach are not called in a child suite

I'm not sure if I'm understanding your use-case properly. Would it be possible to create a simple example that showcases what you want to achieve? It sounds to me like...

Consider enable of parallelism inside framework.

Cons from my POV: - Adds a lot of complexity test-wise, especially when we want to support it on numerous database versions - Will probably make debugging and maintainability harder...

Database disconnect every time when I trying to install the framework

@jgebal Maybe something we could fail-safe? Or give an expressive error message? Don't know the capabilities of SQL*Plus enough - in SQLcl it would be possible.

BE_BETWEEN should report better on Type mismatch

I would like to implement this myself

BE_BETWEEN should report better on Type mismatch

Haha, please pick it up. Once I find time and energy to get into the project again, I have loads of stuff to do with cli and java-api

STUB/MOCK qeury result

From my point of view, the main problem might be the design of your `actual_code` procedure. Yes, you *can* probably "stub" a query with a sys_refcursor, but what you're most...

Documentation: Mark specific topics/features with "available since <version>"

Maybe also add some indication of whether and how some features can be utilized with cli and SQLDeveloper plugIn. @PhilippSalvisberg @jgebal thoughts?

Documentation: Mark specific topics/features with "available since <version>"

Valid point - I thought more about the different run-possibilities. I'll try an approach and request your feedback then :)

utPLSQL V2-3-1 not creating synonym and ut_i_spool_temp.sql not found

Hey @hichem19alg utPLSQL V2-3-1 is 5 years old and not maintained as a separate project. I'm really sorry, but we won't be able to help you with that, unless you...