ssb-dbgen | Star Schema Benchmark dbgen | Database library

by electrum C Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | ssb-dbgen Summary

ssb-dbgen is a C library typically used in Database applications. ssb-dbgen has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.

note: in our research paper we use the ssb instead of ssbm version of 2/28/10: cardinality of supplier fixed to follow benchmark spec: now 2000*sf (previously was 10000*sf, in error): line 226, driver.c type of time value changed from long to time_t (now 64 bits on windows): line 688, build.c building in visual studio 2008: use win32 console project, not using precompiled headers, in properties>c/c++>commandline, additional options: /d "ssbm" /d "dbname" /d "db2" (for db2) building using makefile_win: set for db2 build: nmake -f makefile_win (change database symbol for other database). ssbm is based on tpc-h dbgen source. the coding style and architecture follows the tpch dbgen. the original tpch dbgen code stays untouched and all new code related to ssbm dbgen follow the "#ifdef ssbm" statements. for original detailed tpc-h documentation, please refer tpch_readme document under the same directory. here we just list few things that are specific to ssbm. same idea as tpch dbgen setup, which requires user to create an appropriate makefile, using makefile.suite as a basis. make sure to

Support

Quality

Security

License

Reuse

Support

ssb-dbgen has a low active ecosystem.

It has 83 star(s) with 48 fork(s). There are 2 watchers for this library.

It had no major release in the last 6 months.

There are 5 open issues and 1 have been closed. There are 3 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of ssb-dbgen is current.

Quality

ssb-dbgen has 0 bugs and 0 code smells.

Security

ssb-dbgen has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

ssb-dbgen code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

ssb-dbgen does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

ssb-dbgen releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

It has 570 lines of code, 0 functions and 1 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of ssb-dbgen

Get all kandi verified functions for this library.

ssb-dbgen Key Features

No Key Features are available at this moment for ssb-dbgen.

ssb-dbgen Examples and Code Snippets

No Code Snippets are available at this moment for ssb-dbgen.

Community Discussions

Trending Discussions on ssb-dbgen

How do I indicate I'm "merged" with a fork I'm already up-to-date with?

QUESTION

How do I indicate I'm "merged" with a fork I'm already up-to-date with?

Asked 2017-Dec-01 at 19:19

I'm developing a fork of some FOSS project on GitHub, for which I've looked into all other forks and incorporated all relevant changes. But - I've done that work not via pull-requests, but just using simple manual patches.

Now, I would like to claim that my fork has merged with the other forks. Unfortunately, if I try to create a pull request for one of them using GitHub, the interface tells me my fork is already up-to-date so a pull request is unnecessary.

Can I circumvent that somehow? Perhaps with command-line git commands?

... to be more concrete: My project, a fork I want to get pull request from.

...

ANSWER

Answered 2017-Dec-01 at 19:19

So in your repository, click new Pull request. In the next page, select:

your own eyalroz/ssdbgen as 'base fork', and the other alanbernstein/ssdbgen as head fork - and make sure to select the branch with the latest commit for the other repository.

like here: https://github.com/eyalroz/ssb-dbgen/compare/master...alanbernstein:month-typo-fix

After creating this, your project should have a new open Pull request, that you can merge.

Source https://stackoverflow.com/questions/47594535

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install ssb-dbgen

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: