After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 137547 - Database requires table name prefix
Database requires table name prefix
Status: RESOLVED OBSOLETE
Product: planner
Classification: Other
Component: Database
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: planner-maint
planner-maint
Depends on:
Blocks:
 
 
Reported: 2004-03-18 00:23 UTC by Lincoln Phipps
Modified: 2021-06-09 20:29 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description Lincoln Phipps 2004-03-18 00:23:56 UTC 
When you run projects on hosted services they generally give you just one
database (or rather they cost per database). Into this you stick all your
application database tables. Its traditional that applications are able to
prefix the tables with something so that there is very little chance of a
name clash.

Ideally planner should do this too. We could hardcode the prefix as
"planner" but also allow the user to change this in some sort of option
(e.g. command line option). That would allow test and live projects to
reside within one database. Very handy (essential) for migration testing.

Rgds,
Lincoln.
Comment 1 Lincoln Phipps 2004-04-17 03:23:42 UTC 
Hint to me: Store this prefix value in the actual database itself in the
"planner" table e.g. give it a name like planner_tables_prefix.

Then when we open the database we retrieve this and then from that point on we
use this value. Thus its very flexible and nothing needs to be hard coded except
the initial planner table name.
Comment 2 GNOME Infrastructure Team 2021-06-09 20:29:39 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/World/planner/-/issues/46.