Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
Documentation
Project
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
2
Issues
2
List
Board
Labels
Milestones
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
snac
Documentation
Commits
ba2405f9
Commit
ba2405f9
authored
Aug 04, 2015
by
twl8n
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
updating the plan
parent
24401c29
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
1 deletion
+1
-1
plan.md
tat_requirements/plan.md
+1
-1
No files found.
tat_requirements/plan.md
View file @
ba2405f9
...
...
@@ -67,7 +67,7 @@ Code we write<a name="code-we-write"></a>
-
*maybe, discuss*
change vocabulary.sql from insert to copy. It would be smaller and faster, although in reality as soon as
it is in the database, the text file will never be touched again.
-
<a
name=
"tags"
>
</a>
*discuss*
c
an/should we create a tag system to deal with ad-hoc requirements later in the project? The tags
-
<a
name=
"tags"
>
tag system
</a>
discuss; C
an/should we create a tag system to deal with ad-hoc requirements later in the project? The tags
are very similar to vocabulary entryies in that the tag values are controlled. The difference being a weaker
moderation of tags and more readiness to create new tags (types). The tag table would consist of tag, value
and is essentially a name-value system. If we create tags, should we try to enforce some data typing, that
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment