|
How is database design different from program design?
Started by Lodle on
, 6 posts
by 6 people.
Answer Snippets (Read the full thread at stackoverflow):
I would say database between program ....
Database design is more concerned about efficient & simplest persistence of our program and the result is database design.
Errr, seriously?
The premises are entirely different.
|
|
What do I have to consider in database design for a new application which should be able to support the most common relational database systems (SQL Server, MySQL, Oracle, PostgreSQL ...)?
Is it even worth the effort? What are the pitfalls?
Started by splattne on
, 18 posts
by 17 people.
Answer Snippets (Read the full thread at stackoverflow):
What you need....
These are the wrong answers and only lead to pain interpretations .
They will often say only talk to the database via stored procs to abstract out any sql.
Is to not use database specific sql and just code to ansi standards.
|
|
Hi, I want to design a database which will keep record for financial transaction.I want to design it as a product so that it can be used for any type of financial transaction.Are there some design principles specific to financial transaction database ...
Started by sahil garg on
, 3 posts
by 3 people.
Answer Snippets (Read the full thread at stackoverflow):
You will find database design principles for financial systems that are all that different when working with databases never hurt anyone:
Database Design Best Practices
Do you source control from from any database....
|
Ask your Facebook Friends
|
I tried to design the ui with some ui mocking software, but i found it's hard for me to settle down all the detail of the design, since the database didn't design yet.
But if i first design software, then the same problem occur, I didn't have the UI, ...
Started by MemoryLeak on
, 8 posts
by 8 people.
Answer Snippets (Read the full thread at stackoverflow):
That this approach has is that it doesn't prejudice the UI with a particular database design or vice versa that suffered from letting the database design drive the UI design?
Edit: As others have pointed out, you need....
|
|
I would like to know which is the common practice for a domain implementation. Designing the business objects first, that need persistence or the database schema first, generating it from an entity relationship diagram (and afterwards the ORM poco*'s)...
Started by Aggelos Mpimpoudis on
, 3 posts
by 3 people.
Answer Snippets (Read the full thread at stackoverflow):
You don't have to necessarily make the initial design following strict....
Keeping this is mind when designing a database helps.
To the database side of things mainly because databases are the ones that are harder to scale.
|
|
Hello,
I have a relatively large database tables (just under a million rows) that has mapping like this:
(int, int, int, int) ----> (float, float)
Not all possible int combinations map to a float pair.
Here is where my knowledge of database design ...
Started by Goro on
, 3 posts
by 3 people.
Answer Snippets (Read the full thread at stackoverflow):
If you are using the database for data-mining then this gives quick:
database_[a's value here....
Database access works that for common sequences of its.
If the mapping is deterministic over time, then you can also cache the results .
|
|
I have just installed the GDR RTM version of Visual Studio Team System Database Edition GDR RTM.
It all seems to work wonderfully, but I seem to have to edit XML (Database.sqlpermissions) for specify SQL Permissions.
Am I missing something?
For that matter...
Started by BlackMael on
, 3 posts
by 3 people.
Answer Snippets (Read the full thread at stackoverflow):
Source....
Instead of graphic designers I design tables in database using SQL directly and deploy new database version or continue to make changes in the database directly this version.
It, it is looking better and better.
|
|
I want to design a database for my application, and I have a question about the way to define a relation between the entities.
I have 2 related entities which ID is compound. For example:
an address entity which are identified by the properties [street...
Started by Andy on
, 3 posts
by 3 people.
Answer Snippets (Read the full thread at stackoverflow):
Whether or not you have G UID the second....
The only proper way to design this (common) 1:n relationship is:
Address PhoneNumber *ID <---+ *ID StreetNumber.
Which is bad.
Records in the database that use it as soon as the data changes.
|
|
I know how that question looks, but I'm quite serious. I am trying to create an application that will help me in learning databases (sql, queries, proper database design, etc). I'm using a pet project at work so I have something to focus on with actual...
Started by romandas on
, 4 posts
by 4 people.
Answer Snippets (Read the full thread at stackoverflow):
The database itself can be ....
The general pattern that is followed nowadays is:
Database -> DAL -> BLL.
To create a layer of abstraction from the Model, the Data Access layer which handles all database editor and go to town.
|
|
Database design question for y'all. I have a form (like, the paper kind) that has several entry points for data. This form has changed, and is expected to change over years. It is being turned into a computer app, so that we can, among other things, quit...
Started by Thanatos on
, 5 posts
by 5 people.
Answer Snippets (Read the full thread at stackoverflow):
I think....
Proper database design is a complicated subject; you may do well to pick up a good / your fieldname lookup / etc.)
But the design should probably also depend on how you intend to use for proper table description.
Use Nulls.
|
