dbUpdateAnnotation           package:maDB           R Documentation

_C_r_e_a_t_e _a_n_d _u_p_d_a_t_e _a_n _a_n_n_o_t_a_t_i_o_n _t_a_b_l_e _i_n _a _P_o_s_t_g_r_e_S_Q_L _d_a_t_a_b_a_s_e.

_D_e_s_c_r_i_p_t_i_o_n:

     'dbUpdateAnnotation' this handy function help you to easily create
     an annotation database in a database and to keep the annotation in
     the database up to date.

_U_s_a_g_e:

     dbUpdateAnnotation(Con,data,chip,date,do.backup=TRUE,v=TRUE)

_A_r_g_u_m_e_n_t_s:

     Con: A connection object (create it with the dbConnect.PgSQL.conn
          function from the package RdbiPgSQL)

    data: The annotation table. The column names of the table have to
          be '"id","gen_bank","description","uni_gene","locuslink"'.
          The order of the columns is not important.

    chip: An identifier for the chip or array (oligo set)
          respectiveley.

    date: The date when the annotation was created (better said the
          annotation was up to date).

do.backup: If a backup of the annotation table should be done. This is
          usefull when the annotation of an already existing table is
          going to be updated. By default the annotations of the chip
          that will be updated will be saved as a tab delimited txt
          file. The file name of the txt file consists of the chip and
          the date and the file will be saved in the current workspace.

       v: If TRUE additional information will be printed to the
          console.

_D_e_t_a_i_l_s:

     When creating or updating the database not all columns have to be
     submitted in the 'data' argument, when submitting a table with
     only some of the columns the other columns in the database will
     remain empty.

_A_u_t_h_o_r(_s):

     Johannes Rainer

_R_e_f_e_r_e_n_c_e_s:

_S_e_e _A_l_s_o:

     'dbGetAnnotation'

