Send Netdot-devel mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://osl.uoregon.edu/mailman/listinfo/netdot-devel
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Netdot-devel digest..."
Today's Topics:
1. names of PostgreSQL tables (William Bulley)
----------------------------------------------------------------------
Message: 1
Date: Tue, 4 Mar 2014 09:34:03 -0500
From: William Bulley <[email protected]>
Subject: [Netdot-devel] names of PostgreSQL tables
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
The enhancements to Netdot here at the University of Michigan may
involve one or more new PostgreSQL tables. What do developers think
would be the best way to name these tables? For example, a local
table for networks will be called "Network" which should not cause
any conflicts, but a similar but different "Device" table might.
The original plan was to call the new "Device" table "Device2", but
this caused conflicts with the way PostgreSQL names constraints.
Several possibilities under consideration are:
1) suffix: DeviceUM or DeviceMich
2) prefix: UMdevice or MDevice
3) other: Equipment
Would it be better to completely avoid similar names for tables, or
are there any benefits to using method #2 above whereby all local
changes at UofM would be grouped together when the tables are listed
alphabetically?
Regards,
web...
--
William Bulley Email: [email protected]
72 characters width template ----------------------------------------->|
------------------------------
_______________________________________________
Netdot-devel mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-devel
End of Netdot-devel Digest, Vol 84, Issue 1
*******************************************
