]> jfr.im git - irc.git/blob - software/RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2002/000123.html
rename -> *.git
[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices-coding / 2002 / 000123.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices Coding] Re: idea about database names
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Re%3A%20idea%20about%20database%20names&In-Reply-To=">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="000121.html">
11 <LINK REL="Next" HREF="000124.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices Coding] Re: idea about database names</H1>
15 <B>Andrew Church</B>
16 <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Re%3A%20idea%20about%20database%20names&In-Reply-To="
17 TITLE="[IRCServices Coding] Re: idea about database names">achurch at achurch.org
18 </A><BR>
19 <I>Tue Jan 22 09:46:44 PST 2002</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="000121.html">[IRCServices Coding] something to put on your todo list ??
22 </A></li>
23 <LI>Next message: <A HREF="000124.html">[IRCServices Coding] Cosmetic Bug with Enforcer
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#123">[ date ]</a>
27 <a href="thread.html#123">[ thread ]</a>
28 <a href="subject.html#123">[ subject ]</a>
29 <a href="author.html#123">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>&gt;&gt;<i> &gt;&gt; The way MySQL works, it would be easier for AKILL, S-lines and other
35 </I>&gt;&gt;<i> &gt;&gt; operserv things to be handled in one database
36 </I>&gt;&gt;<i>
37 </I>&gt;&gt;<i> So use tables for crying out loud.
38 </I>&gt;<i>
39 </I>&gt;<i>Well I thought it would be kind of a hack if the AKILL table had a
40 </I>&gt;<i>different name for every database. I guess what I'm really getting at is
41 </I>&gt;<i>to have the database names under the database module instead of under
42 </I>&gt;<i>the individual modules.
43 </I>
44 The current database system works the same way and I don't see any
45 problems with it. Besides, if you do want to do it all in one table,
46 there's nothing that says you can't do it that way... though I do see
47 what you're getting at with database/table names. I'll think about it.
48
49 --Andrew Church
50 <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org</A>
51 <A HREF="http://achurch.org/">http://achurch.org/</A>
52
53 </PRE>
54
55 <!--endarticle-->
56 <HR>
57 <P><UL>
58 <!--threads-->
59 <LI>Previous message: <A HREF="000121.html">[IRCServices Coding] something to put on your todo list ??
60 </A></li>
61 <LI>Next message: <A HREF="000124.html">[IRCServices Coding] Cosmetic Bug with Enforcer
62 </A></li>
63 <LI> <B>Messages sorted by:</B>
64 <a href="date.html#123">[ date ]</a>
65 <a href="thread.html#123">[ thread ]</a>
66 <a href="subject.html#123">[ subject ]</a>
67 <a href="author.html#123">[ author ]</a>
68 </LI>
69 </UL>
70
71 </body></html>