An error occurred fetching the project authors.
  1. 10 Apr, 2006 1 commit
  2. 13 Feb, 2006 1 commit
  3. 31 Jan, 2006 1 commit
  4. 20 Jan, 2006 1 commit
    • stewart@mysql.com's avatar
      WL#2868 Fix backup trigger handling · d88e5766
      stewart@mysql.com authored
      BACKUP previous set up triggers using DICT.
      This lead to all kind of trouble.
      An smaller alternative to using SUMA for backup
        is to just make BACKUP handle triggers to TUP directly.
      
      This way all triggers will be totally local,
        and error handling is much simpler.
      
      --- old impl.
      
      Start: Master recives GSN_DEFINE_BACKUP_CONF from all participants
      Master sends CREATE_TRIG_REQ for all tables to local DICT (dict master)
      Master sends START_BACKUP_REQ to all paricipants with trigger ids from DICT
      Master sends ALTER_TRIG_REQ (online) to local DICT
      Master waits for GCP
      Master starts distributed scan
      When scan has finished
      Master waits for GCP
      Master sends DROP_TRIGGER to local DICT
      Master sends STOP_BACKUP_REQ to all participants
      
      --- new impl.
      
      Start: Master recives GSN_DEFINE_BACKUP_CONF from all participants
      Master sends START_BACKUP_REQ to all paricipants
        Participand sends CREATE_TRIG_REQ for all tables to local TUP
      Master waits for GCP
      Master starts distributed scan
      When scan has finished
      Master waits for GCP
      Master sends STOP_BACKUP_REQ to all participants
        Participant sends DROP_TRIGGER to local TUP
      
      Changes:
      All trigger handling is _local_
       This implies, that abort (e.g due to node failure) can be _local_
      
      
      fix testBackup test so that it will run successfully with the (now correct)
      backup trigger code.
      d88e5766
  5. 07 Nov, 2005 1 commit
  6. 27 Apr, 2005 1 commit
  7. 22 Apr, 2005 1 commit
  8. 19 Jan, 2005 1 commit
  9. 16 Dec, 2004 1 commit
  10. 13 Dec, 2004 1 commit
  11. 09 Dec, 2004 1 commit
    • joreland@mysql.com's avatar
      bug#6995 - ndb · 0ab8c723
      joreland@mysql.com authored
      don't store keys in normalized form
      instead save everythings as normal attributes               
      0ab8c723
  12. 29 Nov, 2004 1 commit
    • tomas@poseidon.ndb.mysql.com's avatar
      aligned backup errorcodes with rest of ndb error codes giving it range from 1300 · b11f3feb
      tomas@poseidon.ndb.mysql.com authored
          added new error type "configuration or application error"
          Added check if backup is issued during diskless mode, backup refuse returned
          added possibility to get error code as a result from management client
          addded possibility to set connecstring with CONNECT command
          changed to use strcasecmp instead of strcmp
          added possibility to run one command on cammand client to ndb_mgm and get an errorcode of command fails
          made thread safe veriosn of getErrorText in management server
          aligned backup errorcodes with rest of ndb error codes giving it range from 1300
          print error message from regular ndberror struct
          added new arrer type "cofiguration or application error"
          commented on allocaded ranges for errors
      b11f3feb
  13. 23 Aug, 2004 1 commit
  14. 01 Aug, 2004 1 commit
  15. 26 May, 2004 1 commit
  16. 14 Apr, 2004 1 commit