On Fri, 2008-12-19 at 16:33 +0100, Pascal Craponne wrote:
> DBML generated files should be complete, as complete as C# files,
> since those DBML files can be used as source to generate C#. Isn't it
> the case for you?

No.

awill...@linux-nnci:~/tmp/DbLinq> mono
DbMetal.exe /provider=PostgreSql  
/conn="database=OGo;username=OGo;host=localhost"  -namespace:Org.OpenGroupware 
/entityBase:OGoEntity   /code=OGoDB.cs -database:OGo 
awill...@linux-nnci:~/tmp/DbLinq> wc -l OGoDB.cs
21251 OGoDB.cs

This contains what looks like a full assembly of classes, whereas -

awill...@linux-nnci:~/tmp/DbLinq> mono
DbMetal.exe /provider=PostgreSql  
/conn="database=OGo;username=OGo;host=localhost"  -namespace:Org.OpenGroupware 
/entityBase:OGoEntity   /dbml=OGoDB.dbml -database:OGo 
awill...@linux-nnci:~/tmp/DbLinq> wc -l OGoDB.dbml 
161 OGoDB.dbml

Nothing but:

<?xml version="1.0" encoding="utf-8"?>
<Database xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; Name="&quot;OGo&quot;"
EntityNamespace="Org.OpenGroupware" ContextNamespace="Org.OpenGroupware"
Class="OgO" BaseType="DbLinq.Data.Linq.DataContext"
Provider="PostgreSql"
xmlns="http://schemas.microsoft.com/linqtosql/dbml/2007";>
  <Table Name="public.address" Member="Address">
    <Type Name="Address" />
  </Table>
    .... more empty <Table ..><Type .../></Table> entries .....
</Database>

So it contains no associations and no field name data.

DbLinq Database mapping generator 2008 version 0.18.0.0
mono-core-2.0.1-18.1.i586
Linux linux-nnci 2.6.25.18-0.2-pae


> On Fri, Dec 19, 2008 at 16:04, Adam Tauno Williams
> <[email protected]> wrote:

> On Thu, Dec 11, 2008 at 17:57, Adam Tauno Williams
> > > I've just started trying out DbLinq,  I can generate source for my
> > > database without issue.  But I'd like to clean up how the schemais
> > > presented;  DbMetal has the option
> > >       /aliases:<file>                   Use mapping file.
> > > But I can't find any docs on how to construct such an alias file;
>  I
> > > a ssume I must be googling the wrong terms.   I thought perhaps
> > > Ineeded
> > > >to make a DBML file and then process that, like
> > mono DbMetal.exe /provider=PostgreSql
> > > /conn="database=OGo;username=OGo;hostlocalhost"  \
> > > /dbml=OGoDB.dbml -database:OGo \
> > > -namespace:Org.OpenGroupware /entityBase:OGoEntity
> > > - but the file it generated is extremely sparse (which is possibly
> > > correct, I guess).
> On Thu, 2008-12-11 at 19:05 +0100, Pascal Craponne wrote:
> > here are two kinds samples of rename files in the source code
> > (in src/DbMetal):
> > - xml files (DbMetal specific), pgsqlFieldRenames.xml and
> >  oraFieldRenames.xml
> > - DBML files (I started to implement something to get closer to the
> >  original SqlMetal), like NorthwindRename.dbml  There are still some
> >  problems, but  it works fine for columns and classes (less fine for
> > associations).
> Is there a way to generate a default DBML that contains all the
> dataand
> then edit it, or do I have to create it from scratch?  When I do
> "/dbml=OGoDB.dbml" the DBML file is *very* sparse and contains only
> references to tables (no references to fields), like:
>  <Table Name="public.article" Member="Article">
>    <Type Name="Article" />
>  </Table>
> But if I generate classes they do domain setter/getters for all the
> fields.
> The alias method (like pgsqlFieldRenames.xml) seems to work for both
> fields and tables, so that may be sufficient;  just seems like DBML is
> the richer solution.

-- 
          Consonance: an Open Source .NET OpenGroupware client.
 Contact:[email protected]   
http://freshmeat.net/projects/consonance/


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"DbLinq" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/dblinq?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to