On Mon, 30 Apr 2007 17:23:11 +0200, Loic Dachary <[EMAIL PROTECTED]> wrote: > Ryan McLean <[EMAIL PROTECTED]> writes: > >> Hi, >> >> Could you please review >> > http://pokersource.info/developers/specifications/Database-Specification.html >> in particular the Inconsistencies section? > > I did not realize the int(10) <-> int(11) inconsistency.
See #2 below.. :) > It occured to me that you should omit the precise datatype from the > documentation. Otherwise it will be soon out of sync. You are interested > by > the semantic level, right ? > Tbph i am interest in both. The reason for documenting the sizes is 2 fold: 1. Allows developers to code restrictions into their program eg web forms they can limit the sizes programatically & are aware that there are size restrictions.. 2. Allows developers to find inconsistencies in both the database and program, eg the game could look for an int but recieve a float. As to going out of sync.. well once I have the specification there ANY changes to the database should be replicated here by the developer committing the change (using your out of sync argument if noone updates / maintains this once its done ANY change to the db will result in it being out of sync). > A word about users table > > skin_url : player.male or player.female (not really a url but could be > in the future) > skin_outfit : an XML snipet fit for osgcal that describes the outfit of > the 3d character > > skin_image : binary image data for the 2d avatar of the player (unused > by poker2d but > otherwise supported by the library) > skin_image_type : mime type of the skin_image (image/png only supported > currently) Thanks I'll update that now. _______________________________________________ Pokersource-users mailing list [email protected] https://mail.gna.org/listinfo/pokersource-users
