Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 63966 invoked from network); 6 Mar 2002 14:26:02 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 6 Mar 2002 14:26:02 -0000 Received: (qmail 202 invoked by uid 97); 6 Mar 2002 14:25:55 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 184 invoked by uid 97); 6 Mar 2002 14:25:54 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 170 invoked from network); 6 Mar 2002 14:25:53 -0000 Reply-To: From: "John Gregg" To: "'Tomcat Developers List'" Subject: RE: [PATCH] change JDBCRealm to add flexibility in table layout Date: Wed, 6 Mar 2002 08:25:46 -0600 Message-ID: <000001c1c51a$cf02bfd0$75c8a8c0@ws03> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal In-Reply-To: <80F5674514B4D311BAFC0040F6A45EEE243670@ntserver> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I assumed increased flexibility + backwards compatibility would be welcome. After all, Tomcat has to serve the needs of many different users. Some of those users, including me, are working for clients who aren't willing to spend the money on things like WebLogic or Oracle. Instead, we use Tomcat, which works great, and databases like PostgreSQL and MySQL. As you've shown with the views, as a PostgreSQL user, I don't absolutely NEED the patch I've provided, but I consider it an improvement nonetheless because I value flexible designs. I would expect the MySQL users to appreciate a solution that works for everyone, not just everyone else. After this patch, I was considering cleaning up some of the exception handling issues in JDBCRealm, but from now on I'll confine myself to ordinary bug fixes and not design "improvements." john -----Original Message----- From: tomcat-dev-return-6703-john.gregg=techarch.com@jakarta.apache.org [mailto:tomcat-dev-return-6703-john.gregg=techarch.com@jakarta.apache.or g]On Behalf Of Ignacio J. Ortega Sent: Tuesday, March 05, 2002 1:43 PM To: 'Tomcat Developers List'; 'john.gregg@techarch.com' Subject: RE: [PATCH] change JDBCRealm to add flexibility in table layout ( Syntax aproximated maybe sql-92, more or less ) create table users ( user_id integer not null primary key, user_name varchar(15) not null , user_pass varchar(15) not null ); create table user_roles ( role_id integer not null primary key, user_id integer not null, role_name varchar(15) not null ); create view user_roles_jdbcrealm as select u.user_name,ur.role_name from user_roles ur join users u on (ur.user_id=u.user_id) and use this view in jdbcrealm.. Please add what you need to be able to understand you.. Saludos , Ignacio J. Ortega -- To unsubscribe, e-mail: For additional commands, e-mail: