• Resolved fotiik

    (@fotiik)


    Po nowej instalacji niestety i aktywacji wtyczki bazowej pojawia się błąd. Wcześniej nie miałem tego problemu. pierwszy raz się to zdarzyło.
    Włączenie wersji pro niczego nie poprawia.

    Table ‘gbt8f_gjmaa_settings’ already exists i tak z innymi tabelami

    Błąd bazy danych WordPressa [Table 'gbt8f_gjmaa_settings' already exists]
    CREATE TABLE GbT8F_gjmaa_settings (setting_id INT AUTO_INCREMENT NOT NULL,setting_name VARCHAR (255) NOT NULL,setting_site VARCHAR (255) NOT NULL,setting_is_sandbox INT (2) NULL DEFAULT 0,setting_webapi_key VARCHAR (255) NULL,setting_login VARCHAR (255) NULL,setting_password VARCHAR (255) NULL,setting_client_id VARCHAR (255) NULL,setting_client_secret VARCHAR (255) NULL,setting_client_token TEXT NULL,setting_client_token_expires_at DATETIME NULL,setting_client_refresh_token TEXT NULL,setting_user_country VARCHAR (2) NULL DEFAULT "PL",setting_user_city TEXT NULL,setting_user_province TEXT NULL,setting_user_postcode TEXT NULL,setting_auction_closed INT(2) NULL DEFAULT 0,setting_sync INT NULL DEFAULT 1, PRIMARY KEY (setting_id)) CHARACTER SET utf8 COLLATE utf8_bin;
    
    Błąd bazy danych WordPressa: [Table 'gbt8f_gjmaa_profiles' already exists]
    CREATE TABLE GbT8F_gjmaa_profiles (profile_id INT AUTO_INCREMENT NOT NULL,profile_setting_id INT NOT NULL,profile_name VARCHAR (255) NOT NULL,profile_type VARCHAR (255) NULL,profile_category VARCHAR (255) NULL,profile_sort VARCHAR (255) NULL,profile_user VARCHAR (255) NULL,profile_search_query VARCHAR (255) NULL,profile_last_sync DATETIME NULL,profile_auctions INT NULL,profile_import_step INT NULL,profile_import_lock INT (2) NULL DEFAULT 0,profile_imported_auctions INT NULL,profile_all_auctions INT NULL,profile_clear_auctions INT (2) NULL DEFAULT 0,profile_to_woocommerce INT (2) NULL DEFAULT 0,profile_sync_price INT (2) NULL DEFAULT 0,profile_sync_stock_date DATETIME NULL,profile_sync_status_date DATETIME NULL,profile_sync_price_date DATETIME NULL,profile_cron_sync INT (2) NULL DEFAULT 1,profile_errors INT (11) NULL DEFAULT 0,profile_error_message TEXT NULL, PRIMARY KEY (profile_id)) CHARACTER SET utf8 COLLATE utf8_bin;
    
    Błąd bazy danych WordPressa: [Table 'gbt8f_gjmaa_auctions' already exists]
    CREATE TABLE GbT8F_gjmaa_auctions (id INT AUTO_INCREMENT NOT NULL,auction_id BIGINT NOT NULL,auction_profile_id INT NOT NULL,auction_name VARCHAR (255) NOT NULL,auction_price FLOAT (10,2) NULL,auction_bid_price FLOAT (10,2) NULL,auction_images TEXT NULL,auction_seller BIGINT NULL,auction_attributes TEXT NULL,auction_categories TEXT NULL,auction_time DATETIME NULL,auction_quantity INT NULL,auction_clicks BIGINT NULL DEFAULT 0,auction_visits BIGINT NULL DEFAULT 0,auction_sort_order INT NULL,auction_updated_at DATETIME NULL,auction_status VARCHAR(30) NULL DEFAULT "ACTIVE",auction_in_woocommerce INT NULL DEFAULT 0,auction_woocommerce_id INT NULL DEFAULT 0, PRIMARY KEY (id)) CHARACTER SET utf8 COLLATE utf8_bin;
    
    Błąd bazy danych WordPressa: [Table 'gbt8f_gjmaa_categories' already exists]
    CREATE TABLE GbT8F_gjmaa_categories (id INT AUTO_INCREMENT NOT NULL,category_id VARCHAR (255) NOT NULL,category_parent_id VARCHAR (255) NOT NULL,name VARCHAR (255) NOT NULL,country_id INT NULL,leaf SMALLINT NULL DEFAULT 0,created_at DATETIME DEFAULT NOW(), PRIMARY KEY (id)) CHARACTER SET utf8 COLLATE utf8_bin;
    • This topic was modified 5 years, 10 months ago by fotiik.
Viewing 4 replies - 1 through 4 (of 4 total)
Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Table ‘*_gjmaa_settings’ already exists’ is closed to new replies.