Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you are not firmly oposed to doing some coding :-) getting <a href="http://code2code.net/DB_Linq/" rel="nofollow noreferrer">LINQ to MySql, Oracle and Postgress</a> and modifying it would probably save you a lot of work as well. Remember that LINQ to SQL still uses the same ADO.NET connection.</p> <p>Beware that LINQ to Entities is not the same as LINQ to SQL and even if you get that IBM lib working you'll first have to check if you are going to be allowed to use it against existing DB without a lot of proofing (it can easily trip and try to modify existing DB - check out this thread if you want to dig into it that aspect: <a href="http://social.msdn.microsoft.com/Forums/en-US/adodotnetentityframework/thread/f3a5b27a-5b73-476a-8c38-1eaedc8f197c" rel="nofollow noreferrer">http://social.msdn.microsoft.com/Forums/en-US/adodotnetentityframework/thread/f3a5b27a-5b73-476a-8c38-1eaedc8f197c</a>).</p> <p>You can also go to <a href="http://www.ibm.com/developerworks/forums/thread.jspa?threadID=203893&amp;tstart=0&amp;messageID=14212368#14212368" rel="nofollow noreferrer">IBM's Entity Framework Beta thread</a> (start from the end where some ppl claimed working results). </p> <p>Important thing is not to try to get absolutely everything that MS SQL got - you just need table representation classes and you are good to go for the first round.</p> <p>One other thing you could try is to open normal ADO.NET connection to DB2 (or force ODBC if it turns out that non-ODBC connection is too snoopy and sensitive) to DB2, and try acting like it's SQL Server so to speak. If it turns out that <a href="http://msdn.microsoft.com/en-us/library/bb386987.aspx" rel="nofollow noreferrer">SqlMetal</a> agrees to work with that connection you are pretty much done - it will autogen table representation classes for you.</p> <p>If it balks, you'll need MS SQL Server as well, at lest for development purposes. For a start script out a few tables from DB2, create then in SQL Server and then run SqlMetal and look into the source code. You'll see that it creates pretty clan classes for table representation and just puts hefty but straight forward attributes on them -- meaning easy to copy&amp;paste or even generate by a good script. Once you see how a small autogenned file looks like you'll also see that you can attach more code to provided hooks or remove some existing code. Check that <a href="http://code2code.net/DB_Linq/" rel="nofollow noreferrer">LINQ to MySql etc.</a> again.</p> <p>LINQ itself just needs table representation classes so you'll be reasonably free to make your own System.Data.Linq.DataContext derivative almost to your heart's desires and I suppose that the schema in DB2 hardly ever changes so you won't need to change it too frequently. LINQ is pretty open system in general (as evidenced by many <a href="http://blogs.msdn.com/b/charlie/archive/2008/02/28/link-to-everything-a-list-of-linq-providers.aspx" rel="nofollow noreferrer">LINQ to something</a> libs) meaning that if modifying DataContext derivative is not enough you can take over the whole LINQ expressions as well.</p> <p>Once you have a proof of concept with a few tables you may need to write a perl or python script (or powershell or C#) to do a little regex replacing if DB2-s table creation scripts don't run on SQL Server intact (there's always a few syntax deviations) and you really have take the logest route.</p>
    singulars
    1. This table or related slice is empty.
    1. POGenerating LINQ to DB2?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USZXX
    1. USZXX
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POGenerating LINQ to DB2?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. CORolling my own from that DBLinq project just might be the ticket. I'll have to work with one of our DB2 people on the query syntax and all that, but as you say I'm really just looking for the absolute simplest data access. Selecting columns from tables is about 99% of the goal, which would be pretty good.
      singulars
      1. PO
      1. USDavid
    2. COI'd expect DB2 to have completely standard SQL syntax for all normal LINQ needs (queryes, inserts, updates). But I would expect some diffs in scripts that whatever UI/mgmt tool it has generates to script the creation of a table and admin stuff like that and there might be few data types that are different or just have diferent names so you may have to "not support" some of them for the time being.
      singulars
      1. PO
      1. USZXX
    3. COThat's likely the case. For our needs the most common data type by far is character fields. Though, if I remember from my last experience with DB2 years ago, that's a common field in general. I remember the DBAs there telling me that "bool" isn't an option and I needed to use the characters "T" and "F" instead. Though that may have just been them. Just to show them the absurdity of it I instead made a 5 character field and used "Is" and "No is" :) It's not the turnkey solution I'd hoped for, but it's the best so far. Bounty's yours.
      singulars
      1. PO
      1. USDavid
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload