DB LINQ - v0.13 released

What’s in it?

Work on large DBs, composite PKs, PostgreSql schemas, self-joins, bug fixes …

Download from google.

14 Responses to “DB LINQ - v0.13 released”

  1. boomhauer Says:

    Was curious about something, since a lot of the work involved in making a Linq provider to a database is in building methods of pulling all the db info out (schema/keys/relationships kinda stuff), if the recently-opensourced MyGeneration code generation framework might not be a help in this regard.. .it has “generic” metadata querying method for almost any know db out there. not that it would be used for code gen (though it could maybe?) but more for reusing the schema abstraction parts..

  2. Mladen Says:

    Does this release work with the release version of VS2008? If not, any idea of when an update is coming?

  3. george Says:

    Hi boomhauser - thanks for pointing me to MyGeneration - have not seen it before. I will go read about it - anything that retrieves DB schema in DBML format can help us. But at the moment, most serious problems are on the the provider side, and I am less worried about the codegen/SqlMetal side.

    And Mladen - yes it does work in VS2008 release version.

    Regards, Jiri George

  4. laurent morisseau Says:

    Hi,
    thanks for your job.
    I have noticed that you didn’t implement blob and longblob in SQLMetal for mysql. I wish to use your provider on a mysql db using longblob.
    Do you plan to implement those types?

    regards,
    laurent

  5. Dave Joyner Says:

    Similar to Laurent’s comment — mysql schema with BIGINT gets mapped to UInt64 which doesn’t seem to be handled.

    I worked around by adding GetUInt64 & GetUInt64N to DataReader2.cs and this to RowEnumeratorCompiler.cs

    else if (t2 == typeof(UInt64))
    {
    minfo = typeof(DataReader2).GetMethod(”GetUInt64″);
    }

    I’m not sure if that is the right approach (but it does work).

    Ideas?

    Thanks for the excellent library

  6. Anton Andreev Says:

    I really appreciate your work and I intend to use DB LINQ a lot.

    How long to you intend to support DB LINQ. I do not want to write my software with a library that may cease support in the next 6 months.

    Cheers,
    Anton

  7. george Says:

    Dave - Thanks for spotting the MySql BIGINT problem.
    I have just checked in a fix, and created a testDB called ‘AllTypes’ for future testing. Please let me know if it works for you.

    And Anton - apologies, but at the moment DBLinq does not comes with any support. About as reliable as my employer …
    However, Oracle is working on an official provider…

  8. Anton Andreev Says:

    What should I do if I want to become a developer to dblinq and commit some bugfixes to the provider myself? Please write me e a personal email.

  9. Anton Andreev Says:

    I have reported some issues. When do you expect do add fixes to svn or let me do it myself?

  10. Farshid Says:

    There is some errors on Oracle DB linq ver 0.14 :
    the first and important problem is about generated the primary keys.
    If table had more than 1 primary key It doesn’t work correct.
    and second problem is about DataField Types that the beter types is here:
    public static string mapSqlTypeToCsType(string dbType, decimal? precision)
    {
    switch(dbType)
    {
    case “NUMBER”:
    return “decimal”;
    case “VARCHAR2″:
    return “string”;
    case “TIMESTAMP”:
    return “DateTime”;
    case “CHAR”:
    return “string”;
    case “NVARCHAR2″:
    return “string”;
    case “DATE”:
    return “DateTime”;
    case “BLOB”:
    return “byte[]”;
    case “LONG”:
    return “Int64″;
    default:
    return “UnknownOracleType_20 //(Unprepared for Oracle type “+dbType+”) \n”;
    }
    }

  11. Farshid Says:

    I Implemented the code for making Camel notation and paskal notation from oracle fields. if you need I can send it for you. but I’m in iran and I can get the code from google If the code be in other site it’s better for me.

  12. Farshid Says:

    About 2 post ago: Problem is not in multy primary key but it is when a table has more than one firigen key from a table

  13. Anton Andreev Says:

    You did not answer to my questions, you neither comment some of the issues I have found or fix them. You did not tell how to become a member of the project. I am considering branching your code (dblinq).

  14. george Says:

    Farshid, Anton, apologies for not responding to this weblog.
    Most of the conversation has moved to a newsgroup here:

    http://groups.google.com/group/dblinq

    Can you start posting there?
    Thanks,
    Jiri

    PS. Farshid - can you access googlecode.com? Can you access groups.google.com? I know users from Cuba are having problems with googlecode.
    PPS Farshid - I checked in your changes.

Leave a Reply