dataobjectsdotnet - Project Hosting on Google Code

Today 8 hours ago 4 new revisions pushed by alex.yakunin - a268f41777:- Issue #499: Implement object-to-object (O2O) mapper - Minor fix in Prefetch subsystem 41972ade0d:- TypeIdUpgrade test e13cc1a990:- TypeIdUpgrade issue resolver e6324eac94:- Localization sample refactoring. a268f41777:- Issue #499: Implement object-to-object (O2O) mapper - Minor fix in Prefetch subsystem 41972ade0d:- TypeIdUpgrade test e13cc1a990:- TypeIdUpgrade issue resolver e6324eac94:- Localization sample refactoring. Last 7 days Dec 26, 2009 Revision 036b898d04 (LINQ bugfix - constant expression fix) pushed by alex.yakunin - LINQ bugfix - constant expression fix LINQ bugfix - constant expression fix Dec 26, 2009 3 new revisions pushed by alex.yakunin - 55c8302b71:Localization sample 3e4713cfcf:- Single or SingleOrDefault exception 7a1d85e46c:LINQ exceptions message 55c8302b71:Localization sample 3e4713cfcf:- Single or SingleOrDefault exception 7a1d85e46c:LINQ exceptions message Dec 25, 2009 10 new revisions pushed by alex.yakunin - ffa533425d:Addressed issue #533: Full-text search implementation 06850cbc77:- Added logging of SQL parameters. dbbc2f17a9:Xtensive.Messaging => Unused Xtensive.TransactionLog => Unused Xtensive.PluginManager => Unused Xtensive.Distributed.Core => Unused Xtensive.Distributed.Test => Unused b8d31ace74:- Tests for nulls handling in the prefetch subsystem are added - Nulls handling is fixed d7d0054323:Addressed issue #533: Full-text search implementation 6f09dad581:- HeaderParseTest 2fa2623eb8:- Logging chapter has been updated. 3551e6fa30:Entity indexer supportLINQ: Persistent Indexer Accessor (Entity Reference) 27aff2fd7d:- Russian localized strings were replaced with spanish ones. d4005375b8:Indexer WHERE test ffa533425d:Addressed issue #533: Full-text search implementation 06850cbc77:- Added logging of SQL parameters. dbbc2f17a9:Xtensive.Messaging => Unused Xtensive.TransactionLog => Unused Xtensive.PluginManager => Unused Xtensive.Distributed.Core => Unused Xtensive.Distributed.Test => Unused b8d31ace74:- Tests for nulls handling in the prefetch subsystem are added - Nulls handling is fixed d7d0054323:Addressed issue #533: Full-text search implementation 6f09dad581:- HeaderParseTest 2fa2623eb8:- Logging chapter has been updated. 3551e6fa30:Entity indexer supportLINQ: Persistent Indexer Accessor (Entity Reference) 27aff2fd7d:- Russian localized strings were replaced with spanish ones. d4005375b8:Indexer WHERE test Dec 25, 2009 issue 532 (Current Sql logger doesn't log parameter values) Status changed by denis.krjuchkov - Status: Done Status: Done Dec 24, 2009 Revision 14c6fb6fcf (Few more reports are added.) pushed by alex.yakunin - Few more reports are added. Few more reports are added. Dec 24, 2009 issue 561 (Evaluate SQL Server Compact 3.5 SP1 for Windows Desktop) reported by Dmitri.Maximov - Subj. Subj. Dec 24, 2009 Revision 1629f468b2 (Dependency matrices are updated.) pushed by alex.yakunin - Dependency matrices are updated. Dependency matrices are updated. Dec 24, 2009 2 new revisions pushed by alex.yakunin - 7fed2c7006:- Logging chapter has been updated. fc53270c5c:Added most interesting reports from NDepend code analysis. 7fed2c7006:- Logging chapter has been updated. fc53270c5c:Added most interesting reports from NDepend code analysis. Dec 24, 2009 8 new revisions pushed by alex.yakunin - b9e16b5b69:No comment. c369297e09:Query<T> -> Query bugfix in project templates. f510017b77:Storage.Manual: prefetch test is added. da30a87967:- Minor fixes. 028d3b98bc:Type level logging is implemented. 4ec6ec70f1:Manual: CoreServices sections is written. 8d2c218e6b:- Public prefetch API is changed 5cf96ede2d:- Handling of nulls in prefetch subsystem is fixed - PrefetchTest is improved b9e16b5b69:No comment. c369297e09:Query<T> -> Query bugfix in project templates. f510017b77:Storage.Manual: prefetch test is added. da30a87967:- Minor fixes. 028d3b98bc:Type level logging is implemented. 4ec6ec70f1:Manual: CoreServices sections is written. 8d2c218e6b:- Public prefetch API is changed 5cf96ede2d:- Handling of nulls in prefetch subsystem is fixed - PrefetchTest is improved Dec 24, 2009 issue 560 (Any PersistentAccessor and EntitySetAccessor method must val...) reported by alex.yakunin - Subj. Currently we don't do this, and thus it's possible to use CoreServices from hackersDomain in protectedDomain. Subj. Currently we don't do this, and thus it's possible to use CoreServices from hackersDomain in protectedDomain. Dec 23, 2009 6 new revisions pushed by alex.yakunin - 6674f0c239:Storage.Manual project update (unification). 956d393fce:Storage.Manual project update (fixes). a638c616d9:- Issue #499: Implement object-to-object (O2O) mapper 35d18647a9:Added issue #559 : using EntitySet<T> as query root error e948da5f25:LINQ: Persistent Indexer Accessor cb9b134f39:- Logging chapter has been started. 6674f0c239:Storage.Manual project update (unification). 956d393fce:Storage.Manual project update (fixes). a638c616d9:- Issue #499: Implement object-to-object (O2O) mapper 35d18647a9:Added issue #559 : using EntitySet<T> as query root error e948da5f25:LINQ: Persistent Indexer Accessor cb9b134f39:- Logging chapter has been started. Dec 23, 2009 issue 559 (using EntitySet<T> as query root error) Status changed by alexis.kochetov - Is not reproducible Status: Invalid Is not reproducible Status: Invalid Dec 23, 2009 issue 559 (using EntitySet<T> as query root error) reported by alexis.kochetov - From your example about using EntitySet<T> as query root, I tried: Code: Select all var subTopic = (from topic in Query.All<Topic>() where topic.Name == topicName select topic).SingleOrDefault<Topic>(); EntitySet<Subscription> subscriptions = subTopic.Subscriptions; var subscription = from sub in subscriptions where sub.ApplicationName == ApplicationName select sub; but the where in the last line is highlighted with the following error: "Delegate 'System.Func<NNet.Broker.Subscription,int,bool>' does not take '1' arguments" From your example about using EntitySet<T> as query root, I tried: Code: Select all var subTopic = (from topic in Query.All<Topic>() where topic.Name == topicName select topic).SingleOrDefault<Topic>(); EntitySet<Subscription> subscriptions = subTopic.Subscriptions; var subscription = from sub in subscriptions where sub.ApplicationName == ApplicationName select sub; but the where in the last line is highlighted with the following error: "Delegate 'System.Func<NNet.Broker.Subscription,int,bool>' does not take '1' arguments" Dec 23, 2009 issue 558 (Refactor tests in Storage.Manual project) reported by alex.yakunin - That's for unification. Storage.Manual must be ready to be studied by customers. So: - All the tests there must look like CustomLinqCompilerTest - LazyLoadingTest, CheatSheetTest are other good examples. Key rules: - its own namespace Xxx for each [TestFixture] - #region Model there - #region for each essential part there (service, etc.) - Test class name: XxxTest - If there is a single [Test] method, it must be named MainTest; otherwise they must be named YyyTest - If there is a set of test methods, use var domain = GetDomain() as it's shown in CustomLinqCompilerTest. var domain must be used in GetDomain as well - in this case it will be easy to cite the code in Manual. That's for unification. Storage.Manual must be ready to be studied by customers. So: - All the tests there must look like CustomLinqCompilerTest - LazyLoadingTest, CheatSheetTest are other good examples. Key rules: - its own namespace Xxx for each [TestFixture] - #region Model there - #region for each essential part there (service, etc.) - Test class name: XxxTest - If there is a single [Test] method, it must be named MainTest; otherwise they must be named YyyTest - If there is a set of test methods, use var domain = GetDomain() as it's shown in CustomLinqCompilerTest. var domain must be used in GetDomain as well - in this case it will be easy to cite the code in Manual. Dec 23, 2009 issue 557 (Refactor DomainConfiguration.Types usage: it must properly s...) reported by alex.yakunin - I'd like to have a single point for configuring: - Available persistent types - IModules // currently they're detected by completely different way - Compiler containers - Session & Domain-level services (e.g. new IQueryPreprocessor is Domain- level service): in fact, we must add them to default IoC resolvers. - Possibly, even IoC default resolvers. Custom IoC resolvers must work - nearly as it happens now. DomainConfiguration.Types is actually a good candidate to be this point: if you register a whole assembly or namespace, it must expose all these types available in it. To implement this refactoring, we must: - Add exclusion mechanism there. It must be useful. I.e. TypeRegistry.Skip(...) - Fix current filtering condition there to appropriate (more types must "pass" it) - Filter its result, when it's used - Replace IModule search code to the appropriate one - etc. The idea is to provide a convention over configuration pattern for all this stuff like we did with persistent types. I'd like to have a single point for configuring: - Available persistent types - IModules // currently they're detected by completely different way - Compiler containers - Session & Domain-level services (e.g. new IQueryPreprocessor is Domain- level service): in fact, we must add them to default IoC resolvers. - Possibly, even IoC default resolvers. Custom IoC resolvers must work - nearly as it happens now. DomainConfiguration.Types is actually a good candidate to be this point: if you register a whole assembly or namespace, it must expose all these types available in it. To implement this refactoring, we must: - Add exclusion mechanism there. It must be useful. I.e. TypeRegistry.Skip(...) - Fix current filtering condition there to appropriate (more types must "pass" it) - Filter its result, when it's used - Replace IModule search code to the appropriate one - etc. The idea is to provide a convention over configuration pattern for all this stuff like we did with persistent types. Dec 23, 2009 2 new revisions pushed by alex.yakunin - 987a2b4577:Addressed issue #533: Full-text search implementation - Index definitions 9525a5a418:LINQ: Persistent Indexer Accessor 987a2b4577:Addressed issue #533: Full-text search implementation - Index definitions 9525a5a418:LINQ: Persistent Indexer Accessor Dec 22, 2009 4 new revisions pushed by alex.yakunin - a69a888839:Localization sample 4333c7352d:- Issue #499: Implement object-to-object (O2O) mapper 4ef6efd709:No comment. 7e4e65858c:LINQ: Persistent Indexer Accessor a69a888839:Localization sample 4333c7352d:- Issue #499: Implement object-to-object (O2O) mapper 4ef6efd709:No comment. 7e4e65858c:LINQ: Persistent Indexer Accessor Dec 22, 2009 issue 500 (Implement visual model designer based on VS.NET DSL tools) commented on by alex.yakunin - Alex Ilyin were able to implement a really nice prototype of this in ~ one week; moreover, the code were was relying not on T4-based code generation, but on itergration with VS.NET code model to update the source code. Finally we've made a decision we must follow this way - if this is done, it will be possible to use both graphical model editor and update the code manually - i.e. it's very similar to class diagrams in VS.NET. Currently we paused this part of work: actually it was not quite interesting for users that voted for features during the most recent poll, so we decided we must just evaluate the approach and estimate the complexity (several man-month to get pretty good designer) for now. We'll return back to this issue when most important ones are closed. Alex Ilyin were able to implement a really nice prototype of this in ~ one week; moreover, the code were was relying not on T4-based code generation, but on itergration with VS.NET code model to update the source code. Finally we've made a decision we must follow this way - if this is done, it will be possible to use both graphical model editor and update the code manually - i.e. it's very similar to class diagrams in VS.NET. Currently we paused this part of work: actually it was not quite interesting for users that voted for features during the most recent poll, so we decided we must just evaluate the approach and estimate the complexity (several man-month to get pretty good designer) for now. We'll return back to this issue when most important ones are closed. Dec 22, 2009 issue 500 (Implement visual model designer based on VS.NET DSL tools) commented on by malisa.ncube - this would be quite interesting to have, but not vital. this would be quite interesting to have, but not vital. Last 30 days Dec 22, 2009 Revision 4fae258b69 (- Query<T> is eliminated at all.) pushed by alex.yakunin - - Query<T> is eliminated at all. - Query<T> is eliminated at all. Dec 21, 2009 issue 554 (Attempt to enumerate EntitySet leads to 2 queries, if Count>...) Labels changed by alex.yakunin - Labels: Performance Labels: Performance Dec 21, 2009 issue 35 (Custom type discriminator columns (custom type of TypeId col...) Status changed by alex.yakunin - AFAIK, done. See [TypeDiscriminator] attribute description in Manual. Status: Done AFAIK, done. See [TypeDiscriminator] attribute description in Manual. Status: Done Dec 21, 2009 14 issues changed by alex.yakunin - Issues 93, 349, 383, 447, 448, 472, 473, 474, 479, 516, 518, 523, 525, 527 Issues 93, 349, 383, 447, 448, 472, 473, 474, 479, 516, 518, 523, 525, 527 Dec 21, 2009 issue 451 (Local collections support in caching enviroment.) Labels changed by alex.yakunin - Labels: Milestone-Release4.1 Component-Storage.Linq Labels: Milestone-Release4.1 Component-Storage.Linq Dec 21, 2009 issue 484 (Add filtering in provider) Labels changed by alex.yakunin - Labels: Milestone-Release4.1 Labels: Milestone-Release4.1 Dec 21, 2009 issue 452 (Order by error) Labels changed by alex.yakunin - Labels: Milestone-Release4.1 Labels: Milestone-Release4.1 Dec 21, 2009 issue 535 (Eliminate Query<T>) Labels changed by alex.yakunin - Labels: Milestone-Release4.1 Labels: Milestone-Release4.1 Dec 21, 2009 issue 539 (LINQ query throws NotSupportedException used with DevExpress...) Labels changed by alex.yakunin - Labels: Milestone-Release4.1 Labels: Milestone-Release4.1 Dec 21, 2009 issue 535 (Eliminate Query<T>) commented on by alex.yakunin - I finally removed Query<T> at all. LINQ translator already does not support it, so I decided to, well, simplify everything a bit. I finally removed Query<T> at all. LINQ translator already does not support it, so I decided to, well, simplify everything a bit. Dec 21, 2009 issue 551 (UpgradingDomainBuilder.ProvideTypeId does not take Metadata....) commented on by alex.yakunin - Serialized model = model from "Metadata.Extensions" table. This isn't really bad, if you use DO properly, but such a behavior is completely unexpected for hackers (= clever developers) trying to manually modify "Metadata.Type". So we must fix this. Serialized model = model from "Metadata.Extensions" table. This isn't really bad, if you use DO properly, but such a behavior is completely unexpected for hackers (= clever developers) trying to manually modify "Metadata.Type". So we must fix this. Dec 21, 2009 issue 553 (Upgrade from v4.0.X to latest v4.1 leads to data lost in Per...) commented on by alex.yakunin - P.S. PerformSafely simply won't work. P.S. PerformSafely simply won't work. Dec 21, 2009 5 new revisions pushed by alex.yakunin - 89b416ed12:Localization sample 31837e6a4d:- DisconnectedState & Transactions: Two bugs were fixed, another two bugs were found. 50df56ad23:Merged Manual is updated. a7334dea78:Sandbox projects update (Query<T> -> Query). 033df77f66:- Query<T> build action is set back to "Compile". Class is marked as [Obsolete]. - Implemented issue #535 : Eliminate Query<T> 89b416ed12:Localization sample 31837e6a4d:- DisconnectedState & Transactions: Two bugs were fixed, another two bugs were found. 50df56ad23:Merged Manual is updated. a7334dea78:Sandbox projects update (Query<T> -> Query). 033df77f66:- Query<T> build action is set back to "Compile". Class is marked as [Obsolete]. - Implemented issue #535 : Eliminate Query<T> Dec 21, 2009 issue 535 (Eliminate Query<T>) changed by alex.yakunin - Status: Done Owner: alex.yakunin Status: Done Owner: alex.yakunin Dec 21, 2009 2 new revisions pushed by alex.yakunin - e22d7d1b3d:Fixed issue #554 : Attempt to enumerate EntitySet leads to 2 queries, if Count>=32 Implemented issue #555 : Add EntitySet.Prefetch method group b85b833c84:Fixed issue #556 : SessionManager stops committing the transactions at some point e22d7d1b3d:Fixed issue #554 : Attempt to enumerate EntitySet leads to 2 queries, if Count>=32 Implemented issue #555 : Add EntitySet.Prefetch method group b85b833c84:Fixed issue #556 : SessionManager stops committing the transactions at some point Dec 21, 2009 issue 468 (Check: rollback on SessionManager.Demand().HasErrors=true do...) Status changed by alex.yakunin - Closing as likely related to issue 556 Status: Done Closing as likely related to issue 556 Status: Done Dec 21, 2009 issue 556 (SessionManager stops committing the transactions at some poi...) Status changed by alex.yakunin - Status: Done Status: Done Dec 21, 2009 issue 556 (SessionManager stops committing the transactions at some poi...) commented on by alex.yakunin - Fixed in r13391. Fixed in r13391. Dec 21, 2009 issue 556 (SessionManager stops committing the transactions at some poi...) reported by alex.yakunin - Subj. Buggy code: if (Session.Resolver==null) Session.Resolver = () => Session; Must be: if (Session.Resolver==null) Session.Resolver = () => Current.Session; + Ideally we must ensure BeginRequest works as expected even if EndRequest is not invoked by some reason. Subj. Buggy code: if (Session.Resolver==null) Session.Resolver = () => Session; Must be: if (Session.Resolver==null) Session.Resolver = () => Current.Session; + Ideally we must ensure BeginRequest works as expected even if EndRequest is not invoked by some reason. Dec 21, 2009 issue 554 (Attempt to enumerate EntitySet leads to 2 queries, if Count>...) Status changed by alex.yakunin - Done. Status: Done Done. Status: Done Dec 21, 2009 issue 555 (Add EntitySet.Prefetch method group) Status changed by alex.yakunin - Done. Status: Done Done. Status: Done Dec 21, 2009 issue 555 (Add EntitySet.Prefetch method group) reported by alex.yakunin - They must provide a simple way to ensure the whole EntitySet or its part is loaded. They must provide a simple way to ensure the whole EntitySet or its part is loaded. Dec 21, 2009 issue 554 (Attempt to enumerate EntitySet leads to 2 queries, if Count>...) reported by alex.yakunin - Subj. Subj. Dec 21, 2009 issue 553 (Upgrade from v4.0.X to latest v4.1 leads to data lost in Per...) commented on by alex.yakunin - Workaround: - Remove "TypeId" column from "Included Columns" set in "Type.IX_Name" index - Remove "TypeId" column from the following tables: "Metadata.Assembly" "Metadata.Extension" "Metadata.Type" - Start the upgrade to Domain running on DO v4.1. Workaround: - Remove "TypeId" column from "Included Columns" set in "Type.IX_Name" index - Remove "TypeId" column from the following tables: "Metadata.Assembly" "Metadata.Extension" "Metadata.Type" - Start the upgrade to Domain running on DO v4.1. Dec 21, 2009 issue 553 (Upgrade from v4.0.X to latest v4.1 leads to data lost in Per...) reported by alex.yakunin - - Old schema contains TypeId; new one does not - On the other hand, first intermediate (upgrading) domain is built in Validate mode. So leads to validation failure. - This means DO4 has no model & TypeIds during the upgrade, and thus it regenerates them. = Data lost (old data becomes inaccessible). As you see, there are set of issues: - Why DO4 does not "completely fails" here? I.e. why it continues the upgrade ? - We must recognize v4.0 schema (with TypeID columns) and allow upgrading from it safely. - Old schema contains TypeId; new one does not - On the other hand, first intermediate (upgrading) domain is built in Validate mode. So leads to validation failure. - This means DO4 has no model & TypeIds during the upgrade, and thus it regenerates them. = Data lost (old data becomes inaccessible). As you see, there are set of issues: - Why DO4 does not "completely fails" here? I.e. why it continues the upgrade ? - We must recognize v4.0 schema (with TypeID columns) and allow upgrading from it safely. Dec 21, 2009 issue 552 (Implement namespace rename hint) reported by alex.yakunin - Subj. Subj. Dec 21, 2009 issue 551 (UpgradingDomainBuilder.ProvideTypeId does not take Metadata....) reported by alex.yakunin - Subj. So basically, [Metadata.Type] table content isn't used on upgrades; we use only serialized model. Subj. So basically, [Metadata.Type] table content isn't used on upgrades; we use only serialized model. Dec 20, 2009 2 new revisions pushed by alex.yakunin - 3c6a1e78f3:- Issue #499: Implement object-to-object (O2O) mapper 231a82ea56:Localization sample 3c6a1e78f3:- Issue #499: Implement object-to-object (O2O) mapper 231a82ea56:Localization sample Dec 20, 2009 issue 550 (The plug-in "Xtensive.Core.Weaver" was not found) Status changed by alex.yakunin - Ok - thanks for notifying us. Status: Invalid Ok - thanks for notifying us. Status: Invalid Dec 19, 2009 issue 550 (The plug-in "Xtensive.Core.Weaver" was not found) commented on by psulek - Resolved, i have pointing variable $(DataObjectsDotNetPath) to old 'DataObjects.Net.targets' file. When i fixed this, everything is ok! Resolved, i have pointing variable $(DataObjectsDotNetPath) to old 'DataObjects.Net.targets' file. When i fixed this, everything is ok!

issue 557 (Refactor DomainConfiguration.Types usage: it must properly s...) reported by alex.yakunin - I'd like to have a single point for configuring: - Available persistent types - IModules // currently they're detected by completely different way - Compiler containers - Session & Domain-level services (e.g. new IQueryPreprocessor is Domain- level service): in fact, we must add them to default IoC resolvers. - Possibly, even IoC default resolvers. Custom IoC resolvers must work - nearly as it happens now. DomainConfiguration.Types is actually a good candidate to be this point: if you register a whole assembly or namespace, it must expose all these types available in it. To implement this refactoring, we must: - Add exclusion mechanism there. It must be useful. I.e. TypeRegistry.Skip(...) - Fix current filtering condition there to appropriate (more types must "pass" it) - Filter its result, when it's used - Replace IModule search code to the appropriate one - etc. The idea is to provide a convention over configuration pattern for all this stuff like we did with persistent types.

I'd like to have a single point for configuring: - Available persistent types - IModules // currently they're detected by completely different way - Compiler containers - Session & Domain-level services (e.g. new IQueryPreprocessor is Domain- level service): in fact, we must add them to default IoC resolvers. - Possibly, even IoC default resolvers. Custom IoC resolvers must work - nearly as it happens now. DomainConfiguration.Types is actually a good candidate to be this point: if you register a whole assembly or namespace, it must expose all these types available in it. To implement this refactoring, we must: - Add exclusion mechanism there. It must be useful. I.e. TypeRegistry.Skip(...) - Fix current filtering condition there to appropriate (more types must "pass" it) - Filter its result, when it's used - Replace IModule search code to the appropriate one - etc. The idea is to provide a convention over configuration pattern for all this stuff like we did with persistent types.

Today

Last 7 days

Last 30 days