Zitat von Nigel Kukard <[EMAIL PROTECTED]>: > > >> >> Sorry for being unclear. I have of course used the convert-tsql >> >> according to the INSTALL document. The "TINYTEXT" and "DATETIME" seam >> >> to be omitted. >> > >> > I don't think there are any columns which have DATETIME types, they are >> > all integers storing unix timestamps. >> >> The DATETIME is used in "quotas.tsql". > > Fixed. This should be a big integer. > >> The "TINYTEXT" is used all over the place and is not altered by >> convert-tsql. > > Correct. > >> > Send me the output which is given, and another output of which is >> > expected. >> > >> > Sorry I'm on the road at the moment so my access to my test system is >> > limited :( >> >> No need to hurry. For our tests i fix it "by hand". I will try to >> create a diff but need to know if there is some special reason at all >> to use TINYTEXT and not VARCHAR(255) in the first place. > > None whatsoever, VARHCAR(255) may be a more standard choice. > > Anyone got any arguments to support either alternative in > mysql/pgsql/sqlite?
As far as i know TINYTEXT is supposed to be "faster" in MySQL, but i'm not sure if this is actually true and if yes, how much it is. On the other side VARCHAR(n) is ANSI-SQL Standard so it should be the portabel way to store character fields. Regards Andreas -- All your trash belong to us ;-) www.spamschlucker.org To: [EMAIL PROTECTED] ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ policyd-users mailing list policyd-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/policyd-users
