I am running SchemaCrawler through docker container.
I have tables in database ORACLE in which all tables does not have explicit foreign key referential constraints. I want to generate ER diagram with weak associations.
But don't know where to define weak attributes in an attributes file and load them. Can you please guide me.
Please take a look at your previous question, Cannot write output file in schemacrawler. At this point, you will have mounted the "./share" directory to "C:\Program Files\SchemaCrawler\share". You can create the attributes file in that directory. Let us say the file is called "attributes.yaml". You can then refer to it using --attributes-file ./share/attributes.yaml when you run the Docker container.
Related
I want to use Protégé as an ontology manager. The most basic feature would be to see all the ontology files I have in my repo together in a single opened instance of Protégé i.e. a unified view of all the schema I have in a specific folder. It will be like an Ontology library. Can I do this in Protégé?
I know I can merge all the files first and then see the output file in Protégé but I am looking for a better solution.
Thanks.
I am trying to create a unique id and attach it to a LabVIEW file so that later I can read back that id and know I am looking at exactly the same file. I must be able to generate the id and read it back programmatically. The information must be hidden from the user accessing the file and persist across operating systems and storage mediums.
I was thinking of just adding it into the file 'comment' section, but it appears the Windows no longer supports file comments.
Any ideas?
I would suggest using the Set Tag method on the VI (with persistence) and saving multiple copies of the VI using the Save Instrument method, where each copy would then have its own unique value of the tag. Note that the method is defined as a scripting method, so you would probably need to enable scripting in the LV options to access it.
I don't think there's any API for enumerating tags, so there would be no way to find the value unless you know what the tag is called. Obviously, it's encoded somewhere in the VI file itself, and presumably it would be possible to extract a list of tags if you know the structure of the file, but that's not knowledge I would expect most students to have.
I'm not sure if you can call the set tag method from Python using an external connection to VI server, but certainly the LV code for this should be pretty simple - basically a for loop with ID generation, a couple of method calls and saving a CSV file so you can keep track of which ID belongs to which student. If you use existing IDs, you don't even need to generate and save the IDs.
I am using BDD+cucumber+watir framework to automate a website. Folder structure is like this.
Is it possible to maintain all the element Ids(locators)of a page in one file and call it in step definition.
I cannot see the structuring picture but You can either use the PageFactory model structuring for pure POM. If you are used to BDD and want to maintain most part of its features. You can as well store all the element ids to a file called cucumber.yml. You can find the page object gem https://github.com/cheezy/page-object
Create a file called cucumber.yml in your project directory and have all the locators stored in it as like:
LoginPage
emailtextfield: email_text_field_id
You can load this pageelements.yml file using the YAML loader and call this element locator in the stepdefinition like LoginPage[emailtextfield]
Similarly you can categorize this for all the pages, different yml files. This would be a keydriver approach.
I have a number of XSDs that are part of the enterprise definitions for several services at the client.
I would like to be able to take a single XSD and generate a DDIC structure from it (without the use of PI!)
Seeing as you can generate proxies directly from a WSDL, and this also generates structures and data elements from the XSD definitions inside the WSDL, there is obviously already ABAP code that does this.
But do you know what classes/function modules to use to achieve this? Perhaps there is a convenient utility function or class method that takes the XSD as input and generates the relevant DDIC objects?
Some background on why I need this:
Some of the services include variable sections that include a piece of XML containing the data for one of the enterprise XSD entities; I am hoping to have a DDIC representation of these, which I can fill at runtime and then convert to XML to include in the message.
There is a program on the system called SPROX_XSD2PROXY with which you can upload one or more XSD files which will generate proxy objects for you.
You also end up with a service consumer with a corresponding class and what looks like a dummy operation.
The program is fairly short; it uploads the files(s) to an XSTRING, then converts the XSD(s) to WSDL(s) and finally the WSDL(s) to proxy objects using methods of a class called CL_PROXY_TEST_UTILS.
However, the result is satisfactory as it does give me a structure I can work with. And by examining the contents of those methods, it may be possible to build a more fine-tuned tool if I need one.
When generating my DAL files with SubSonic, I'd like the names of the files to be .gen.cs. The main reason for this is that the files are partial classes, and I would like to add some additional implementation details into another source file for the table called .cs. This is somewhat the standard pattern for generated source files , and I'm wondering if its possible with SubSonic? I'm using SubSonic 2.2.
I thought you might be able to do this by using a set of custom templates, but the CS_ClassTemplate.aspx (or VB_ClassTemplate.aspx) doesn't control the file name of the class.
I don't think this is possible.
As an alternative, you can do what I do. I have a "generated" directory, such as \database\generated and then I put my partial classes at \database\custom. As long as the namespaces of the files in the two different directories match (like .database or whatever), then it works fine. By using two different directories, it's easier to find your custom files without looking at the generated ones.