repository

I am creating a special BE module with Extbase and Fluid and I need a domain object which would be representing standard FE user. When I create new domain object called e.g. Feuser and save it, the extension builder creates special repository and also wants to create special table tx_myextkey_feuser in database. But this table already exists as fe_users . Is possible to tell typo3 that the repository for Feuser objects already exists (as fe_users table) and that typo3 should use the existing one? How can I do that? I need it because the extension (including this BE module) needs to have every

Is there a way to automatically sync my forked Github repository's remote master branch ( origin/master ) to an original Github repository's master branch? ( upstream/master ) I ask because I would like my forked remote origin/master branch on Github to always stay up-to-date so that I could save time by not needing to continually pull / rebase & push upstream repository changes into my forked repo's master branch. It is very easy to sync forked repository but question is how ? In this example i am using WorldMapGenerator Repository Go to your forked repository, you can see setting button

In Spring Data project the CrudRepository provides sophisticated CRUD functionality for the entity class that is being managed. public interface CrudRepository<T, ID extends Serializable> extends Repository<T, ID> { <S extends T> S save(S entity); T findOne(ID primaryKey); Iterable<T> findAll(); Long count(); void delete(T entity); boolean exists(ID primaryKey); // … more functionality omitted. } In general, I know what "S extends T" means, i.e. that S, the return type of save operation, must be subtype of T. Why is it necessary to add such as constraint? I think that would be fine doing

I have a git repository with submodules in the directory projects/myRepo and I want to rename the directory to projects/my-repo . According to this question it can simply be done with mv . But in a repo with submodules git keeps telling me fatal: Not a git repository: projects/myRepo/.git/path/to/submodule``` even for git status . Submodule config: [submodule "path/to/submodule"] path = path/to/submodule url = https://github.com/user/projectName.git Somehow the 'internal path' for the submodule does not get updated?! Is there a way to tell git to update these submodule paths? VonC Since Weston

So, I have two main objects, Member and Guild. One Member can own a Guild and one Guild can have multiple Members. I have the Members class in a separate DbContext and separate class library. I plan to reuse this class library in multiple projects and to help differentiate, I set the database schema to be "acc". I have tested this library extensively and can add, delete, and update Members in the acc.Members table. The Guild class is as such: public class Guild { public Guild() { Members = new List<Member>(); } public int ID { get; set; } public int MemberID { get; set; } public virtual Member

I have a repository like that: public class Repository<T> : IRepository<T> where T : class { private readonly IRepositoryContext _repositoryContext; public Repository(IRepositoryContext repositoryContext) { _repositoryContext = repositoryContext; _objectSet = repositoryContext.GetObjectSet<T>(); } public virtual void Update(T entity) { ObjectSet.AddObject(entity); _repositoryContext.ObjectContext.ObjectStateManager.ChangeObjectState(entity, EntityState.Modified); _repositoryContext.SaveChanges(); } } Now that actually works for all scalar properties of the entity, but all the other entities

If i have the following Repository: public IQueryable<User> Users() { var db = new SqlDataContext(); return db.Users; } I understand that the connection is opened only when the query is fired: public class ServiceLayer { public IRepository repo; public ServiceLayer(IRepository injectedRepo) { this.repo = injectedRepo; } public List<User> GetUsers() { return repo.Users().ToList(); // connection opened, query fired, connection closed. (or is it??) } } If this is the case, do i still need to make my Repository implement IDisposable? The Visual Studio Code Metrics certainly think i should. I'm

Ok i read many things about the repository pattern, including Fowler's book. I know pretty good what it is and what it does, however what i'm not quite sure yet is how it is called by factories and/or domain objects. What I understood is that the repository is supposed to act like an in-memory collection of domain object, and the factory is the class in charge of the instance creation: new myDomainObject() With that in mind, it seems obvious that the repository will need a reference to the factory to create new objects from the data source queries. (Repository -> Factory) Domain objects also