database-schema

My Yii2 is setup with PostgreSQL. Instead of using separate database per project, I like to use schema for each project. Problem with later setup is that I can't figure out how to select default schema "defaultSchema" through configuration. I am having a problem with migrations table because it defaults to "public" schema when I run migration command. Default "public" schema also prevents using database user's search_path. Although I set up my db user with "search_path=myschema, public" I still cannot use migrations without additional configuration, because during runtime Yii looks for the

I know there has been a few answer to a couple of questions similar to the one am asking. But their approach didn't look convincing. My question is how would I structure a database for a category that can have books and a subcategory which can also have books? I have already design a database, but am not convinced by the approach. So I would really appreciate if the guys with experience gave me some advice or improvement or a completely different approach. This how my tables look like (bare in mind this is not the actual code) TABLE Category ID user_id -- Foreign key from user name TABLE

Consider this table: +-------+-------+-------+-------+ | name |hobby1 |hobby2 |hobby3 | +-------+-------+-------+-------+ | kris | ball | swim | dance | | james | eat | sing | sleep | | amy | swim | eat | watch | +-------+-------+-------+-------+ There is no priority on the types of hobbies, thus all the hobbies belong to the same domain. That is, the hobbies in the table can be moved on any hobby# column. It doesn't matter on which column, a particular hobby can be in any column. Which database normalization rule does this table violate? Edit Q. Is "the list of hobbies [...] in an arbitrary

I am starting currently using Alfresco CMS. I need to create an "aspect" in my content model which must contains a number of properties as: Aspect: property 1 : String property 2 : int property 3 : int property 4 : long Moreover it must contains two more properties which are composed either of number of properties as: Format: FormatProperty1: int FormatProperty2: int FormatProperty3: int Metadata: list1: List<String> list2: List<String> MetadataProperty 3: boolean I have not yet created neither a simple content model nor an aspect in Alfresco. Based on my previous knowledge in Relational

Is using "view" in db design right method or we should handle it code side? What are the advantages or disadvantages? I see a couple of reasons to use views : Provide a simpler interface : just query the view, and not a dozen tables, doing joins and all Provide an interface that doesnt change (or less often) : Even if you change the structure of the tables, you might be able to modify your view so it still returns the same thing Which means no change is needed in your application's code : it'll still work, as it's using the view, and not directly accessing the tables Only provide an interface

I want my database to support multi Languages for all text values in its tables. So what is the best approach to do that?. Edit1:: E.G. I've this "Person" table: ID int FirstName nvarchar(20) LastName nvarchar(20) Notes nvarchar(max) BirthDate date ........... So if i want my program to support new language "let say French". should i add new column every time i add new language ? So my "Person" table will look like this ID int FirstName_en nvarchar(20) FirstName_fr nvarchar(20) LastName_en nvarchar(20) LastName_fr nvarchar(20) Notes_en nvarchar(max) Notes_fr nvarchar(max) BirthDate date ......

I'm using SQLite, which doesn't support adding a constraint to an existing table. So I can't do something like this (just as an example): ALTER TABLE [Customer] ADD CONSTRAINT specify_either_phone_or_email CHECK (([Phone] IS NOT NULL) OR ([Email] IS NOT NULL)); Are there any workarounds for this scenario? I know: I can add a constraint for a new table, but it isn't new (and it's generated by my ORM, EF Core) I can do a "table rebuild" (rename table, create new one, copy old data, drop temp table) but that seems really complex Ideas Can I somehow make a copy of the table into a new table, with