mvhub-dev team mailing list archive
-
mvhub-dev team
-
Mailing list archive
-
Message #00275
[Merge] lp:~omacneil/mvhub/improve_sql_lib_related_pod into lp:mvhub
Dan MacNeil has proposed merging lp:~omacneil/mvhub/improve_sql_lib_related_pod into lp:mvhub.
Requested reviews:
MVHub devs with commit rights (mvhub-commit)
see commit log
--
https://code.launchpad.net/~omacneil/mvhub/improve_sql_lib_related_pod/+merge/27300
Your team MVHub Developers is subscribed to branch lp:mvhub.
=== modified file 'lib-mvhub/lib/MVHub/CGIAppBase.pm'
--- lib-mvhub/lib/MVHub/CGIAppBase.pm 2010-06-02 19:10:01 +0000
+++ lib-mvhub/lib/MVHub/CGIAppBase.pm 2010-06-10 19:27:27 +0000
@@ -188,8 +188,8 @@
Given the name of a sql SELECT statement, returns the SQL for that
statement. Currently the file the SQL statements are stored in
is: app-mvhub/conf/sql_select.lib, though you should not depend
- on this location. ---And you should need to depend on a hard coded
- path as this is handled internally for you by CGIAppBase.
+ on this location. ---And you should not need to depend on a hard
+ coded path as this is handled internally for you by CGIAppBase.
=head1 SEE ALSO
=== modified file 'lib-mvhub/lib/MVHub/Utils/DB.pm'
--- lib-mvhub/lib/MVHub/Utils/DB.pm 2010-04-06 15:14:41 +0000
+++ lib-mvhub/lib/MVHub/Utils/DB.pm 2010-06-10 19:27:27 +0000
@@ -558,7 +558,94 @@
croak if the database_type in the config file is neither
SQLite or Pg
-
+
+
+=head2 get_dbh
+
+ TODO
+
+=head2 get_full_name
+
+ TODO
+
+=head2 get_hash_of_agencies
+
+ TODO
+
+=head2 get_next_in_sequence
+
+ TODO
+
+=head2 get_program_name
+
+ TODO
+
+=head2 get_sql_insert_statement($SQL_STATEMENT_NAME)
+
+ Given the name of a sql INSERT statement, returns the SQL for that
+ statement. Currently the file the SQL statements are stored in
+ is: app-mvhub/conf/sql_insert.lib, though you should not depend
+ on this location and you should not need to depend on this location
+ as finding the SQL::Library file is handled internally for you.
+
+
+=head2 get_sql_select_statement($SQL_SELECT_STATMENT_NAME)
+
+ Given the name of a sql SELECT statement, returns the SQL for that
+ statement. Currently the file the SQL statements are stored in
+ is: app-mvhub/conf/sql_select.lib, though you should not depend
+ on this location and you should not need to depend on this location
+ as finding the SQL::Library file is handled internally for you.
+
+=head2 get_sql_update_statement
+
+ Given the name of a sql UPDATE statement, returns the SQL for that
+ statement. Currently the file the SQL statements are stored in
+ is: app-mvhub/conf/sql_update.lib, though you should not depend
+ on this location and you should not need to depend on this location
+ as finding the SQL::Library file is handled internally for you.
+
+=head2 insert_one_record
+
+ TODO
+
+=head2 remove_agency
+
+ TODO
+
+=head2 select_agency_programs
+
+ TODO
+
+=head2 select_agency_record
+
+ TODO
+
+=head2 select_program_record
+
+ TODO
+
+=head2 select_records
+
+ TODO
+
+=head2 select_unique_record
+
+ TODO
+
+=head2 translate_agency_name
+
+ TODO
+
+=head2 translate_program_name
+
+ TODO
+
+=head2 update_one_record
+
+ TODO
+
+
=head1 DIAGNOSTICS
Error messages are listed with documentation for sub routines.
Follow ups