Issue 40 in snofyre: Import method to allow a set of data which is not generated within SNOFyre to be the target of queries.

0 views
Skip to first unread message

sno...@googlecode.com

unread,
Mar 7, 2011, 11:05:10 AM3/7/11
to snofy...@googlegroups.com
Status: New
Owner: ----

New issue 40 by tom.seab...@nhs.net: Import method to allow a set of data
which is not generated within SNOFyre to be the target of queries.
http://code.google.com/p/snofyre/issues/detail?id=40

Proposal for a way to import data into SNOFyre rather
than generate the date within it.

This would presumably require not only a data import method but one which
conducted at least the minimum data validation.


sno...@googlecode.com

unread,
Mar 7, 2011, 12:09:32 PM3/7/11
to snofy...@googlegroups.com

Comment #1 on issue 40 by jay.k...@biomedicalontologies.com: Import method
to allow a set of data which is not generated within SNOFyre to be the
target of queries.
http://code.google.com/p/snofyre/issues/detail?id=40

Tom, can this not be done via MySQL workbench? Is there a need for Snofyre
to implement this functionality when you could presumably use the SQL
Import statement?

sno...@googlecode.com

unread,
Mar 7, 2011, 12:17:42 PM3/7/11
to snofy...@googlegroups.com
Updates:
Labels: Type-Enhancement Component-Persistence Priority-Low

Comment #2 on issue 40 by jay.k...@biomedicalontologies.com: Import method

to allow a set of data which is not generated within SNOFyre to be the
target of queries.
http://code.google.com/p/snofyre/issues/detail?id=40

(No comment was entered for this change.)

Reply all
Reply to author
Forward
0 new messages