Hi, Sanjiv
I've already known Scott Ambler as 1 of the main well regarded Agile
Approaches guru ! (bcoz I'm Agile defender! ;-))
Thnx so much for the link! Take it for grant: I'm gonna check it out!! :D
And still in the case u metioned (changing ID), it can be "assembled" with
the use o
"Agile Database Techniques" by Scott Ambler (well regarded DB guru) has an
excellent discussion on the key picking strategy. The short version is that
surrogate keys is most often the right strategy however there are certain
types of data that are commonly accessed by unique identifiers where use o
In the example, I mean the year of entering (starting year) College
(instead of degree). (yeah, my english was not so good this time! :o)
So, in the case u exposed, there is a performance Restriction/Requisite.
(That would be a reason to change Identifying approach.)
Ice-Man
2008/12/15 Nat
Iceman,
In a perfect wolrd there would never be a need to create an artificial
primary key. However once people start using the applications things
tend to get messier.
Using your example, what happens when the student changes majors or
enters a post graduate degree and his ID changes to refelct
I strongly DESAGREE u. Acording Data Modeling (entity-relation modeling)
there isn't any reason to create an ARTIFICAL IDENTIFIER ATTRIBUTE, if there
is a REAL data that can be used as the identifier.
Otherwise u may designate a artifical identifier. Pupils from Colleges
Applicants use to be
Just like Oscar stated, it is generally considered a best practice to have
database primary keys that have no business meaning attached to them. The
example you provide appears as though it probably should be defined as a
unique not null column, but not primary key. But even if you change the
dat
Thanks for your reply and i need an id likes the 05-CS-123 so, i need an auto
generated string to increment the last number, if the client want to use the
assigned then how to mention in model class to assign the @Id value.
Sudhakar
Oscar Alvarez-2 wrote:
>
> Hello,
>
> What's the diference
Hello,
What's the diference between autogenerated Long key and autogenerated String
key???, i mean, if the String is autogenerated, it's not better solution a
Long key?, but if the String key is meaningful for the end user, then you
should define assigned strategy and assign it before save.
Best
Thanks for your reply
Is there any other way to use the auto generator for the string in mysql
or in any other database
please suggest me for this solution..
Sudhakar..
mraible wrote:
>
> If you're going to use Strings for the primary key, you'll have to use
> a type of generator that
If you're going to use Strings for the primary key, you'll have to use
a type of generator that doesn't increment. I've never done this,
hopefully someone else on this list can help you.
Matt
On Fri, Dec 12, 2008 at 5:39 AM, sudhakargupta
wrote:
>
> Hi Matt...
>
>
> Presently i'm working with t
Hi Matt...
Presently i'm working with the appfuse2 struts.. In one of my table i need
to use the String as a primarykey and use foreignkey relations with this
primarykey.
i created a model class primary key setters/getters are
@Id
private String code;
private String getCode() {
retu
11 matches
Mail list logo
