|
From: JP P. <jp....@ti...> - 2003-08-22 07:40:25
|
Hi Lars, Ken will better answer for PetClinic, but looking at the discussions we had here, there is no particular reason, just a choice. You can as well have just a column for each table in a unique "sequence holder" table. Personally, I made another choice in my applications. For different reasons, I have a unique and shared "IDs provider for" the whole application no matter the table. So an ID will be unique not only for the table but the database. They are as always pros and contras. Regards, Jean-Pierre -----Message d'origine----- De=A0: spr...@li... [mailto:spr...@li...] De la part de Lars Fischer Envoy=E9=A0: jeudi 21 ao=FBt 2003 12:44 =C0=A0: spr...@li... Objet=A0: [Springframework-developer] Petclinic and sequences Hi all, is there any reason why Petclinic uses an extra sequence table for every single table ? Wouldn't it be better to have one table for all sequences ? Petclinic is a very small example but imagine an application with 100 tables. Regards Lars ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0 _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |