If you - Alexander - need longer URIs, no problem: provide the patch and I am very sure we find an additional solution. Maybe something called LongUriMySQLAdapter or so ;)
What I - at a first glance - am missing are primary, unique and foreign key constraints. Is there a reason for this? I thought this is possible with MySQL, isn't it?
Oliver
LOMBART Christophe wrote:
if you have an uri greater than 255 char, I'm ok
No problem for the booleans
I'm not sure for the indexes and PK : I have to check
Thanks for your comments,
Christophe
-------- Message d'origine-------- De: Wendt, Alexander [mailto:[EMAIL PROTECTED] Date: mar. 25/11/2003 10:24 Ã: 'Slide Developers Mailing List' Cc: Objet: RE: MySqlRDBMSlAdapter
Sorry, but your schema seems mysql-unlike/wrong to me. And Yes, I know this wasn't the problem in your mail. :-) Don't know how if the uri.uri_string is redefined, but if not varchar(255) doesn't fit (255-char-limit). - BLOB is what has to be. Then: Primary-key is already an index, why double index i.e. uri.uri_id? The is_variables meant to be boolean, nor? - If Yes, int(11) is much to big. - Why don't take tinyint(1) or even varchar(1). I'm not a mysql-expert, but couldn't anyone check this? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
------------------------------------------------------------------------
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
