I am wondering if it's possible to access global configuration variables when defining an evaluator?
i.e.
I define a title of a GROUP in the global configuration.
The evaluator should read the value of that group and render the action depending on the group.
I don't want to hard-code the group, I want to leave a possibility to change it without rebuilding the module.
Can someone tell me weather it's possible?
Thanks a lot
Related
Good afternoon,
I am trying to create a variable in MySQL (5.7), that will persist through restarts. It appears that user created variables will not give me the ability to accomplish this so I am looking at the global variables. These appear to be built-in to MySQL and I cannot seem to find a way to create a new persistent variable.
How can I create a global/system variable in MySQL (5.7) that will persist through restarts?
There is no simple way through the SQL interface or configuration to create new system variables -- they are, after all, "system" variables. Any solution to this that comes to mind would be an advanced operation, like one of these:
modify the MySQL server source code to create a new system variable
modify the MySQL server source code to reintegrate the "deprecated" logic from prior versions, where the old variable and new variable behave the same but the old variable throws a warning when you use it
write a MySQL plugin (in C) whose only purpose is to expose a new system variable, basically a dummy variable that doesn't actually do anything, other than having a default value and maybe being (or giving the appearance of being) writable if needed, in order to keep the application happy
In David Fenton's answer to the question "MS Access (Jet) transactions, workspaces" he states:
I would also say, never pass the workspace -- only pass the objects you've created with the workspace.
Is passing the workspace a bad idea? If so, why?
Additional info:
My intent here is to execute INSERT/UPDATE/DELETE statements from within multiple Subs/Functions but wrap them all in a single transaction.
The base functionality is wrapped up in a class module. I want to be able to isolate multiple instances of the class module, which means I can't just assume my transactions are executing against the default workspace.
I would like to add the following variable from a script task:
"IndexLocation"
String
Value: "http://www.mypage.com"
'Ex.
dts.variables.add("daf")
--Obviously above does not work
You can add variables to a package using Dts.Variables.Add, but I've never tried it myself - wondering why you'd want to create them dynamically in the package rather than set them up in the Variables pane?
How will these variables be used?
If you're adding them programmatically, other components/tasks will not be aware of them, as you would not have set them up during design time.
Or are you accessing them in another script task, which assumes they have been created?
The general practice is to create variables at design time.
Adding variables at runtime could play havoc on variable locking and other internal ssis workings - you can't guarantee the reliability and accessibility of the variable.
/Customers?$skip=30&$top=10
Is there a reason why you need '?' or '&' AND '$' to identify a query parameter?
Is this a case of the implementation leaking into the interface? I dont necessarily want to expose to users the blatant fact that I'm using .NET Data Services. especially, if at a later date I want to change the implementation to another technology...
Or, is there an easy way to disable the need for the '$' to identify a query option?
So it looks like a much more presentable...
/Customers?skip=30&top=10
Thanks
Query string options that start with the $ character are known as System Query Options and denote actions support by ADO.NET Data Services. Basically, this is done to distinguish system-wide "keywords" from model property names.
To solve this issue, you may try rewriting your URLs from /Customers?skip=30&top=10 to /Customers?$skip=30&$top=10 or even transfer this system information in HTTP headers (if this is an option).
Some projects have properties have miscellaneous settings such as: "AllowPayments", "ShowSideBar", "SectionTitle". Really things that don't necessarily fit in to other objects.
How do you guys store these kinds of values? ApplicationSettings? Flat File? Database table?
How do you access them? Static object with properties? DB call?
Would either of these change if you were in a load balanced environment where you would have to synchronize the files across multiple servers?
Environment
ASP.NET 2.0
For me it depends on the context the setting is. If it relates to the data and the domain, i store in the database, if it relates the the application i store in the web.config.
App.Config, or a custom xml configuration file and config service. Key value pair mappings keeps things very simple.
Since you didn't tell which environment you use:
In .NET applications, I use the ApplicationSettings system from Visual Studio. This way you can configure the settings with default values in the designer, and a strongly-typed class to access the values is generated. I usually add a second ApplicationSettings element with the name Persistent in addition to the default Settings, with anything the user configures to go in the Settings object and anything I just save (i.e. window position) to the Persistent object.
This goes for desktop applications.