Displaying 1 to 20 from 20 results

linq2db - Linq to database provider.

  •    CSharp

LINQ to DB is the fastest LINQ database access library offering a simple, light, fast, and type-safe layer between your POCO objects and your database.Architecturally it is one step above micro-ORMs like Dapper, Massive, or PetaPoco, in that you work with LINQ expressions, not with magic strings, while maintaining a thin abstraction layer between your code and the database. Your queries are checked by the C# compiler and allow for easy refactoring.

dbeaver - Free universal database tool and SQL client

  •    Java

Free multi-platform database tool for developers, SQL programmers, database administrators and analysts. Supports any database which has JDBC driver (which basically means - ANY database). EE version also supports non-JDBC datasources (WMI, MongoDB, Cassandra, Redis). You can download prebuilt binaries from official web site or directly from GitHub releases.

soci - SOCI - The C++ Database Access Library. This is official repository the SOCI project.

  •    C++

Originally, SOCI was developed by Maciej Sobczak at CERN as abstraction layer for Oracle, a Simple Oracle Call Interface. Later, several database backends have been developed for SOCI, thus the long name has lost its practicality. Currently, if you like, SOCI may stand for Simple Open (Database) Call Interface or something similar. SOCI library is distributed under the terms of the Boost Software License.

DBShield - Database firewall written in Go

  •    Go

Protects your data by inspecting incoming queries from your application server and rejecting abnormal ones. By adding DBShield in front of database server we can protect it against abnormal queries. To detect abnormal queries we first run DBShield in learning mode. Learning mode lets any query pass but it records information about it (pattern, username, time and source) into the internal database.




SplendidCRM

  •    ASPNET

SplendidCRM is a Customer Relationship Management (CRM) application that was built on the Microsoft technology stack (Windows, IIS, SQL Server, C#, and ASP.NET). The target audiences are companies that need a simple and powerful CRM, but want to take advantage of their existing

t4models - T4 Models

  •    CSharp

T4 models are used to generate POCO's C# code using your database structure.But not data provider packages (install them only if needed to compile your project, T4 models ships it's own data provider assemblies).

loopback-connector-db2 - LoopBack Connector for IBM DB/2

  •    Javascript

IBM® DB2® is the database of choice for robust, enterprise-wide solutions handling high-volume workloads. It is optimized to deliver industry-leading performance while lowering costs. The loopback-connector-db2 module is the LoopBack connector for DB2.The --save option adds the dependency to the application's package.json file.


db2.js - node.js bindings for IBM DB2 Express-C (might work w/ other implementations, too)

  •    C++

The current test code depends on a database I have set up within my development vm. The code will be updated to use the sample database from DB2 later. Requires gcc and g++, node-gyp, node.js.

banking-digitalization-using-hybrid-cloud-with-mainframes - The following journrey will introduce the available Banking APIs published on IBM Bluemix with logical business programs running on the IBM Z Mainframe through a simulated retail bank called MPLbank

  •    Javascript

Read this in other languages: 中国. The following journey will introduce the available Banking APIs published on IBM Bluemix with logical business programs running on the IBM Z Mainframe through a simulated retail bank called MPLbank.

financial-risk-management-using-machine-learning-on-mainframes - This journey accesses a Financial Risk Management API published on IBM Bluemix with Machine Learning on z/OS running on the mainframe through a simulated retail bank system called MPLbank

  •    Javascript

This journey accesses a Financial Risk Management API published on IBM Bluemix with Machine Learning on z/OS running on the IBM Z Mainframe through a simulated retail bank system called MPLbank. This journey accesses a fictitious retail banking system called MPLbank. MPLbank integrates a Financial Risk Management System based on Machine Learning for z/OS. The initial predictive model was designed to deliver a score representing the probability of the capacity of loan refund for a banking customer according to their personal data. On top of these components, an API layer hosted in IBM Bluemix has been set up to deliver a Financial Risk Management API, illustrating an online decision for loans approval.

increase-retail-revenues-leveraging-hybrid-cloud-on-mainframes - To showcase the business challenges that a typical retail company might be experiencing, we share a case study about a fictitious retail company, and how they leverage IBM Z

  •    Javascript

To showcase the business challenges that a typical retail company might be experiencing, we share a case study about a fictitious retail company, which we refer to as Breadbox Groceries. Today, they run three data centers across the country with IT reaching into the stores and distribution centers as well. In the data centers, they host their core Business Support Systems on IBM Z. Supporting applications are hosted on IBM CICS® and IBM z/OS® Db2 systems.

loopback-connector-db2iseries - Loopback connector for DB2 on iSeries

  •    PLSQL

IBM® DB2® for iSeries is the database of choice for robust, enterprise-wide solutions handling high-volume workloads. It is optimized to deliver industry-leading performance while lowering costs. The loopback-connector-db2iseries module is the LoopBack connector for DB2 for iSeries. The --save option adds the dependency to the application's package.json file.

slack-chatbot-database-watson - Code to build a Slackbot to create and search Db2 or PostgreSQL database entries for events and conferences

  •    Javascript

Code to build a Slackbot to create and search Db2 database entries for events and conferences. The Slackbot is backed by the IBM Watson Assistant (Conversation) service. We integrate Slack and Assistant using the Botkit middleware. As an alternative, an IBM Cloud Databases for PostgreSQL database can be used instead of Db2. The related files have an additional .pg. in their name. The directory botkit-app contains the code for the Node.js app based on Botkit. See the tutorial for instructions to deploy it to Cloud Foundry. You can also test and use it locally.

docker-prestodb - Presto server with DB2 connector

  •    Dockerfile

This is a docker image for PrestoDB with Hive connector.

nodejs-idb-connector - A JavaScript (Node

  •    C++

NOTE This package only installs on IBM i systems. Then you can require in your code, as shown below.

nodejs-idb-pconnector - Promise-based DB2 Connector for IBM i

  •    Javascript

Objective: provide a promise-based database connector for DB2 on IBM i. This project is a promise-based wrapper over the idb-connector project that enables the use of modern JavaScript's async/await syntax.

streamsx.jdbc - Supports Streams application to work with databases via JDBC

  •    HTML

The IBMStreams/streamsx.jdbc toolkit project is an open source Streams toolkit project focused on the development of operators and functions that extend IBM Streams ability to interact with database via JDBC. This toolkit implements the NLS feature. Use the guidelines for the message bundle that are described in the Messages and National Language Support for toolkits document.

github-traffic-stats - Manage and automatically collect Github traffic statistics for repositories

  •    Python

This repository contains the code for an IBM Cloud solution tutorial. In the tutorial, we create an application to automatically collect Github traffic statistics for repositories and provide the foundation for traffic analytics. Github only provides access to the traffic data for the last 14 days. If you want to analyze statistics over a longer period of time, you need to download and store that data yourself. The app and the serverless action discussed in this tutorial implement a multi-tenant-ready solution to manage repositories, automatically collect traffic data on a daily or weekly schedule, and to view and analyze the collected data. An additional dashboard specification is available in file dashboard2.json. It allows to render charts like shown in the two screenshots below. Either copy the file to dashboard.json and use it instead of the default dashboard or modify the code to select from given dashboards. Once you created a dashboard on your own, you can export the specification and copy it into a new file, similar to dashboard2.json. The app code automatically replaces the data source URL and the authentication token.