--- Begin Message ---
Well, my database should be able to check some entry data and decide if these
data will be accepted or rejected in a table that records all the received data.
For example: I'll have a table 1 that contains a list of all the equipments that
can send information to the database. The table 2 that records the data sent
should check whether the data is coming from a valid equipment or not. If the
table1 just mention 'machine 1' and 'machine 2', some data coming from 'machine
3' should be rejected.
Juliana
bluejack wrote:
> 10/28/03 8:11:16 AM, "Martijn Tonies" <[EMAIL PROTECTED]> wrote:
>
> >>
> >> If you are trying to determine whether MySQL is a relational database,
> >> the answer is yes.
> >
> >Ehm... the answer is "no".
> >
> >It's getting better, that's for sure.
>
> MySQL may or may not conform to some standard or another, and it may
> or may not perform the tasks that you, personally, want it to, but
> in fact it *is* a relational database, as opposed to a flat file or
> an object database.
>
> I recommended the questioner evaluate her needs against MySQL's
> available feature set, because if you are used to Oracle (or some
> other robust, commercial relational database) you may be surprised
> at some of the differences or absences in MySQL.
>
> But the questioner made it seem as though she was really just
> trying to get a feel for the basics scope of MySQL, and in that
> context, yes, MySQL is designed to a implement a relational
> database model as opposed to some other fundamental type of
> database.
>
> So, what's your laundry list of things MySQL should do?
>
> --bluejack
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
--- End Message ---
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
