Manageability.
Id(surrogate) can be autoincrement so managed by the engine,
Joins are simpler to write.
Imagine a natural key composed of three or more fields.
Practical, with surrogate you can 'book' a record while not knowing yet all
of the values that compose the natural key.
Just a couple of po
thank you all, i think
"You probably wouldn't need Article_Type table if you're going to store
Article_Type value directly."
is my answer.
--
From: "Kyong Kim"
Sent: Saturday, September 12, 2009 8:22 AM
To: "Arthur Fuller"
Cc: "Claudio Nanni"
A) You would probably want to populate the Article.Article_Type column
with Article_Type.ID. You probably wouldn't need Article_Type table if
you're going to store Article_Type value directly.
I would also consider the use of natural primary key vs surrogate
primary key. We've seen good results wi
Hi All!
I have just released PBXT 1.0.09 RC3. Besides bug fixes, this version
includes 2 Beta features:
* XA/2-Phase Commit support
* Native online backup Driver
Details of all changes are in the release notes:
http://primebase.org/download/ChangeLog
Be aware of the fact that you may r
I agree with Claudio. You have your design correct. The only other thing you
need is the uid qualifier. Presumably you are using PHP or some other front
end to present your data. Your front end would request the user's name and
password, saving the uid in a variable and then issuing the select with
A.J., It sounds good to me!
You can be a little confused but you did it well,
It seems you have all you need there.
A) Yes
B) select * from articles A left join article_types AT on A.article_type =
AT.article_types_id
Claudio
2009/9/11 AndrewJames
> This is a bit of a long shot, but i real
This is a bit of a long shot, but i really need some help and or directed to
the best reading resources.
as i begun building my database (as i went along), i now realise i have to
stop coding and sit back and design the database properly before i can go
on.
However i am still unable to wrap
Per Jessen wrote:
> mysql list,
>
> after my upgrade to 5.1.36 I hit this odd little problem:
>
> I have an application which does roughly this:
>
> CREATE TEMP TABLE new LIKE old;
> populate 'new'.
> do some stuff
> TRUNCATE new;
> populate again
>
> This has always worked fine, but after the
