Gustav Brock
Gustav at cactus.dk
Sat Jul 18 09:02:55 CDT 2009
Hi Shamil I don't know, it could be, on the other hand MySQL (Sun and now Oracle) indeed have the programming resources to create the connector the way they prefer - and I think they pay a lot of attention to this because as they wrote in the recent news letter much to my surprise: <quote> For many years, Microsoft Windows has been the most popular development platform and second most popular production platform for organizations developing MySQL applications. </quote> The "CodeOnly for Entity Framework" is exactly what I had in mind. Thanks for the link - looks like I should sign up for that blog. This must be the ultimate goal - to design and specify your database directly in your code at a higher level than manually adding fields and constraints and so on. I better get that VS2010 beta! But right now - with VS2005 and 2008 - you can edit your datatables in VS and, when you press enter, VS writes the changes back to the database. I think this may be what you recall that I previously have referred to. This feature is great but "CodeOnly for Entity Framework" is certainly better. I'll recommend anyone to study the links to the MSDN blog (and the links at those pages about POCO, Plain Old CLR Objects!). If this works, one day you won't look back. /gustav >>> shamil at smsconsulting.spb.ru 18-07-2009 01:28 >>> Hi Gustav, This mySQL Connector, which can be used to work with mySQL DBs from LINQ for EF(?), is probably developed by using "Entity Client" concept/technology: http://blogs.msdn.com/adonet/archive/2007/02/14/entity-client.aspx It may happen somebody will use this technology to develop an MS Access connector - let's hope that happens real soon? Hey, MS MS Access Team - how about doing that there? Another useful technology MS "cooks" there is "CodeOnly for Entity Framework": http://blogs.msdn.com/adonet/archive/2009/06/22/feature-ctp-walkthrough-code-only-for-entity-framework.aspx You mentioned something like that here already - did you mean that "CodeOnly for Entity Framework" technology or just a concept of starting with Domain Model implemented in code/metadata and then using this Domain Model to generate actual (relational) DB model? -- Shamil -----Original Message----- From: dba-vb-bounces at databaseadvisors.com [mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of Gustav Brock Sent: Friday, July 17, 2009 8:39 PM To: dba-vb at databaseadvisors.com Subject: Re: [dba-VB] Using Microsoft ADO.NET Entity Framework with MySQL (was: LINQ for EF Example) Also: New Release of MySQL Connector/Net 6.0.4 (GA) MySQL Connector/Net 6.0.4, a new version of the all-managed .NET driver for MySQL has been released. This is the first post-GA release of the new 6.0 connector and includes several bug fixes from the initial GA release. This release is approved for use in all scenarios and officially supports MySQL servers 4.1 and higher. View the complete list of changes: http://dev.mysql.com/doc/refman/6.0/en/connector-net-news-6-0-4.html Download Now: http://dev.mysql.com/downloads/connector/net/6.0.html /gustav >>> Gustav at cactus.dk 17-07-2009 18:29 >>> Hi all And as an apropos: Live Webinar: For ISVs - Using Microsoft ADO.NET Entity Framework with MySQL Tuesday, August 11, 2009 - 10:00am PDT The Entity Framework is a new technology that was developed by Microsoft and delivered as part of .NET 3.5 SP1. This framework abstracts the relational schema of the database and presents it as a conceptual schema. This is particularly beneficial for ISVs because by working with a conceptual schema, the commercial application developer avoids having to write complicated joins to connect all the related items of data, greatly reducing development time, resources and therefore, COGS. ISV developers can access their data using ORM-like classes, LinQ syntax, or with a new SQL syntax named EntitySQL, all of which further reduce COGS. Register for this Webinar: http://www.mysql.com/news-and-events/web-seminars/display-397.html /gustav