GitXplorerGitXplorer
d

FluentMySQL

public
1 stars
0 forks
0 issues

Commits

List of commits on branch master.
Unverified
d44494c9b87c1eace7760a196d2b85a9d7270839

Added getting started to readme so the entry point is a little more obvious.

ddanielrbradley committed 13 years ago
Unverified
d0c0d3b0c0926948203de8cb6f817c9413dbe077

Removed broken readme project reference and added to solution items.

ddanielrbradley committed 13 years ago
Unverified
6b604cd6b20f53144855a13e3b14e8b9c127c6e3

Merge branch 'add-where'

ddanielrbradley committed 13 years ago
Unverified
00710695c6ec6fe558e2332057ad9bf4a77bdaf1

Implemented where and "AND" queries.

ddanielrbradley committed 13 years ago
Unverified
5e056973d7d4c868240847c33969041297886d8a

Started bashing out where clause, but decided to change direction: going to simplify the object structure of the where clause until I can find a better way of expressing it, and focus on other areas first.

ddanielrbradley committed 13 years ago
Unverified
e316ee0313d1078f54b575a54e9ed639ce36cd87

Decided roughly how I want to use the new where cause.

ddanielrbradley committed 13 years ago

README

The README file for this repository.

Overview

This is framework, hoping to solve a very specific problem: building SQL statements which are easy to validate, refactor and help maximise re-use.

Before coming to write this framework, my experience has been with working with in-house database (leaky) abstraction layers, hand-writing SQL builders within frameworks and also the mybatis (previously Apache iBatis). This project has therefore come out of wanting to have the control of writing pure SQL but with the separation and modularity of writing SQL in a framework such as iBatis.

I can foresee that this project could be useful both as a standalone framework to generate SQL to run manually, but also as a feeder into a project to wrap up the execution and mapping of result sets to objects.

Design Principals

Consistency: The feature-set and design should aim to be one-to-one with the MySQL grammar.

Specific: Want to solve a fairly narrow problem, but solve it well. If this works well, then hopefully the same principals could be applied for other such grammars or frameworks.

Immutability: A single query object should not be able to be modified; rather, new copies should be produced on each modification. This makes the approach more akin to that of functional programming (and F# was also a serious consideration for this project).

Getting Started

I'm currently starting by drawing up some kind of design in the IntegrationTests\Design.cs file. This should act as a pretty good example of the libraries use.