[Library] cDriver - The SQL Driver to End All SQL Drivers

Discussion in 'WIP and Development Status' started by Goblom, Feb 4, 2014.

Thread Status:
Not open for further replies.
  1. Offline


    cDriver was a small idea that popped into my head one day, "Why hasn't anyone make creating SQL Statements easier, faster and just plain simpler?", well cDriver attempts to make creating SQL statements so simple that you need little to no experience to create extremely complicated SQL Statements.

    cDriver supports MySQL and SQLite with plans to support more into the future, but its main focus are those two.

    Current Version: 0.1_Pre-Alpha

    cDriver is still still being worked on and though of, we do not expect it work perfectly at this current time, but we do believe that most of cDriver is functional. We want you test, break, and continue breaking cDriver util we tell you to stop (we probably won't). Doing so will help us better cDriver and continue developing cDriver.

    cDriver can make creating SQL Statements so easy a Steve can do it. It can turn something like
    1. SELECT username FROM ExampleTable WHERE world='redstone_world'
    1. select("username").from("ExampleTable").where("world").equals(world).$().getStatement();

    cDriver comes with a complete set of JavaDocs (not currently completed) and it explains what each method does.

    cDriver is open source and will always be open source, it can be used in a Java Application or a Bukkit plugin, the possibilities are endless.

    How to Use:
    cDriver is (in my opinion) the easiest SQL Driver to use. It comes with a few example (currently only 1 :( ) and the examples are completed documented with example tables and some small methods to get data from that example table.

    In order to use cDriver you need to create a driver statement. This can be done in one of two ways.
    1. private DriverStatement ds = new DriverStatement(DatabaseType.MySQL);
    2. /**
    3. * OR
    4. */
    5. private DriverStatement ds = cDriver.createNewDriverStatement();
    once you create a DriverStatement then you have a few statements you can create; the available statements are: Delete, Do, Insert, Select & Update, everything else is currently under discussion.
    1. ds.delete();
    2. ds.delete(String tabl);
    3. ds.delete(String... tables);
    4. ds.run();
    5. ds.run(String expression);
    6. ds.run(String... expressions);
    7. ds.insert();
    8. ds.insert(String table);
    9. ds.insert(String table, String column);
    10. ds.insert(String table, String... columns);
    11. ds.select(String what);
    12. ds.update(String table_reference);

    Again, We want you test, break, and continue breaking cDriver util we tell you to stop (we probably won't). Doing so will help us better cDriver and continue developing cDriver.

  2. Offline


    You store the javadoc... In the source folder?
  3. Offline


  4. Offline


    Gosh, I just put it in gh-pages :p
  5. Offline


    xTrollxDudex Me no like branching much, but that would be useful.

    Edit: You are welcome to submit pull request ;)
  6. Offline


    It wouldn't be worth without Travis CI, makes your life so much easier since it executes all my build deploy scripts and javadoccing for me :3
  7. Offline


    xTrollxDudex And now ill need to take a look into that... Learn new things every day.
  8. Offline


  9. Offline


    Garris0n Well ****..... cDriver is still pretty unique though.
Thread Status:
Not open for further replies.

Share This Page