1. Este site usa cookies. Ao continuar a usar este site está a concordar com o nosso uso de cookies. Saber Mais.

problema com mysql

Discussão em 'Web Development' iniciada por filjoa, 18 de Janeiro de 2008. (Respostas: 10; Visualizações: 1757)

  1. filjoa

    filjoa Power Member

    viva

    estou a tentar meter a trabalhar no vista o mysql para servir uma pagina com o MAMBO, mas estou com alguns problemas...

    depois de consegui instalar o PHP e o mysql(supostamente mal instalado) nao consigo acabar de configurar o mambo.

    penso que ja dei as permissões todas para escrita e nao sei o que se esta a passar...

    por exemplo no pre-installation check tenho:
    PHP version >= 4.3.0 Yes - zlib compression support Available - XML support Available - MySQL support Available - Note: MySQL Strict Mode is not support configuration.php Writeable Session save path C:\Program Files\PHP\tmp, Writeable
    e logo de seguida é me pedido para eu meter os dados e tal... dp de eu meter e fazer next para o 3 passo tenho um erro do qual nao me consigo safar...

    SQL=BLOB/TEXT column 'comments' can't have a default value:
    - - - - - - - - - -
    # Table structure for table `mos_comment`

    CREATE TABLE `mos_comment` (
    `id` int(11) NOT NULL auto_increment,
    `articleid` int(11) NOT NULL default '0',
    `ip` varchar(15) NOT NULL default '',
    `name` varchar(30) NOT NULL default '',
    `comments` text NOT NULL default '',
    `startdate` datetime NOT NULL default '0000-00-00 00:00:00',
    `published` tinyint(1) NOT NULL default '0',
    PRIMARY KEY (`id`)
    ) TYPE=MyISAM
    = = = = = = = = = =

    SQL=BLOB/TEXT column 'text' can't have a default value:
    - - - - - - - - - -
    # Table structure for table `mos_poll_data`

    CREATE TABLE `mos_poll_data` (
    `id` int(11) NOT NULL auto_increment,
    `pollid` int(4) NOT NULL default '0',
    `text` text NOT NULL default '',
    `hits` int(11) NOT NULL default '0',
    PRIMARY KEY (`id`),
    KEY `pollid` (`pollid`,`text`(1))
    ) TYPE=MyISAM
    = = = = = = = = = =

    SQL=Table 'filjoa.mos_poll_data' doesn't exist:
    - - - - - - - - - -
    # Dumping data for table `mos_poll_data`

    INSERT INTO `mos_poll_data` VALUES (20, 15, '', 0)
    = = = = = = = = = =

    SQL=Table 'filjoa.mos_poll_data' doesn't exist:
    - - - - - - - - - -
    INSERT INTO `mos_poll_data` VALUES (19, 15, '', 0)
    = = = = = = = = = =

    SQL=Table 'filjoa.mos_poll_data' doesn't exist:
    - - - - - - - - - -
    INSERT INTO `mos_poll_data` VALUES (18, 15, '', 0)
    = = = = = = = = = =

    SQL=Table 'filjoa.mos_poll_data' doesn't exist:
    - - - - - - - - - -
    INSERT INTO `mos_poll_data` VALUES (17, 15, 'Scott Adams', 1)
    = = = = = = = = = =

    SQL=Table 'filjoa.mos_poll_data' doesn't exist:
    - - - - - - - - - -
    INSERT INTO `mos_poll_data` VALUES (16, 15, 'Tim Berners-Lee', 0)
    = = = = = = = = = =

    SQL=Table 'filjoa.mos_poll_data' doesn't exist:
    - - - - - - - - - -
    INSERT INTO `mos_poll_data` VALUES (15, 15, 'Linus Torvalds', 0)
    = = = = = = = = = =

    SQL=Table 'filjoa.mos_poll_data' doesn't exist:
    - - - - - - - - - -
    INSERT INTO `mos_poll_data` VALUES (14, 15, 'Bill Gates', 0)
    = = = = = = = = = =

    SQL=Table 'filjoa.mos_poll_data' doesn't exist:
    - - - - - - - - - -
    INSERT INTO `mos_poll_data` VALUES (13, 15, 'Steve Jobs', 0)
    = = = = = = = = = =

    SQL=Table 'filjoa.mos_poll_data' doesn't exist:
    - - - - - - - - - -
    INSERT INTO `mos_poll_data` VALUES (21, 15, '', 0)
    = = = = = = = = = =

    SQL=Table 'filjoa.mos_poll_data' doesn't exist:
    - - - - - - - - - -
    INSERT INTO `mos_poll_data` VALUES (22, 15, '', 0)
    = = = = = = = = = =

    SQL=Table 'filjoa.mos_poll_data' doesn't exist:
    - - - - - - - - - -
    INSERT INTO `mos_poll_data` VALUES (23, 15, '', 0)
    = = = = = = = = = =

    SQL=Table 'filjoa.mos_poll_data' doesn't exist:
    - - - - - - - - - -
    INSERT INTO `mos_poll_data` VALUES (24, 15, '', 0)
    = = = = = = = = = =

    agora perante este erro alguem me sabe dizer o que esta mal...

    abraço
     
  2. filjoa

    filjoa Power Member

    ja instalei o mysql de novo pensando poder ser de me ter enganado na pass por exemplo e continua tudo na mesma...

    alguem me sabe dar uma pista de para onde me posso virar para tentar resolver esta situação?

    abraço
     
  3. tbogas

    tbogas Power Member

    eu tb tenh o vista e uso o wamp5 pode ser algum problema de compatibilidade. Este funciona.
    Cumps
     
  4. slack_guy

    slack_guy Power Member

    Código:
    CREATE TABLE `mos_comment` (
    `id` int(11) NOT NULL auto_increment,
    `articleid` int(11) NOT NULL default '0',
    `ip` varchar(15) NOT NULL default '',
    `name` varchar(30) NOT NULL default '',
    [B]`comments` text NOT NULL [COLOR="Red"]default ''[/COLOR],[/B]
    `startdate` datetime NOT NULL default '0000-00-00 00:00:00',
    `published` tinyint(1) NOT NULL default '0',
    PRIMARY KEY (`id`)
    ) TYPE=MyISAM
    = = = = = = = = = =
    
    - - - - - - - - - -
    # Table structure for table `mos_poll_data`
    
    CREATE TABLE `mos_poll_data` (
    `id` int(11) NOT NULL auto_increment,
    `pollid` int(4) NOT NULL default '0',
    [b]`text` text NOT NULL [COLOR="Red"]default ''[/COLOR],[/b]
    `hits` int(11) NOT NULL default '0',
    PRIMARY KEY (`id`),
    KEY `pollid` (`pollid`,`text`(1))
    ) TYPE=MyISAM
    = = = = = = = = = =
    Os campos do tipo TEXT não podem ter valores DEFAULT.
     
  5. filjoa

    filjoa Power Member

    viva

    eu estou a iniciar-me nisto ... dai a estar tao a nora... fiz o que fiz mas com ajuda de uma bom manual...

    qual pode ser a causa de os TEXT ter valores DEFAULT? para que eu possa procurar o erro....

    abraço
     
  6. filjoa

    filjoa Power Member

    nao sei se isto é ilegal o facto de estar a fazer subir um post mas estou mesmo a precisar de ajuda...
     
  7. slack_guy

    slack_guy Power Member

    Alguém escreveu isso. Onde? não faço ideia. Quem? desconheço. Quando? vá-se lá saber. Tens de investigar isso nos ficheiros que instalaste.
     
  8. spastikman

    spastikman Banido

    Pesquisa nos ficheiros de instalação pela estrutura do sql e remove esses default '' que o slack indicou. Ou isso foi um erro do script que gera essa estrutura e não deveria estar vazio, ou então nem percebo porque é que lá está o default, pois estar ou não estar (tirando o facto de não ser permitido) é igual, Não fazia nada.
     
  9. filjoa

    filjoa Power Member

    viva

    entao dizes que o problema deve estar aqui neste file my.ini que contem isto:

    mas a meu ver parece estar tudo bem S:... alguem me pode ajudar a procurar o erro?



    Código:
    # MySQL Server Instance Configuration File
    # ----------------------------------------------------------------------
    # Generated by the MySQL Server Instance Configuration Wizard
    #
    #
    # Installation Instructions
    # ----------------------------------------------------------------------
    #
    # On Linux you can copy this file to /etc/my.cnf to set global options,
    # mysql-data-dir/my.cnf to set server-specific options
    # (@localstatedir@ for this installation) or to
    # ~/.my.cnf to set user-specific options.
    #
    # On Windows you should keep this file in the installation directory 
    # of your server (e.g. C:\Program Files\MySQL\MySQL Server X.Y). To
    # make sure the server reads the config file use the startup option 
    # "--defaults-file". 
    #
    # To run run the server from the command line, execute this in a 
    # command line shell, e.g.
    # mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
    #
    # To install the server as a Windows service manually, execute this in a 
    # command line shell, e.g.
    # mysqld --install MySQLXY --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
    #
    # And then execute this in a command line shell to start the server, e.g.
    # net start MySQLXY
    #
    #
    # Guildlines for editing this file
    # ----------------------------------------------------------------------
    #
    # In this file, you can use all long options that the program supports.
    # If you want to know the options a program supports, start the program
    # with the "--help" option.
    #
    # More detailed information about the individual options can also be
    # found in the manual.
    #
    #
    # CLIENT SECTION
    # ----------------------------------------------------------------------
    #
    # The following options will be read by MySQL client applications.
    # Note that only client applications shipped by MySQL are guaranteed
    # to read this section. If you want your own MySQL client program to
    # honor these values, you need to specify it as an option during the
    # MySQL client library initialization.
    #
    [client]
    
    port=3306
    
    [mysql]
    
    default-character-set=utf8
    
    
    # SERVER SECTION
    # ----------------------------------------------------------------------
    #
    # The following options will be read by the MySQL Server. Make sure that
    # you have installed the server correctly (see above) so it reads this 
    # file.
    #
    [mysqld]
    
    # The TCP/IP Port the MySQL Server will listen on
    port=3306
    
    
    #Path to installation directory. All paths are usually resolved relative to this.
    basedir="C:/Program Files/MySQL/MySQL Server 5.0/"
    
    #Path to the database root
    datadir="C:/Program Files/MySQL/MySQL Server 5.0/Data/"
    
    # The default character set that will be used when a new schema or table is
    # created and no character set is defined
    default-character-set=utf8
    
    # The default storage engine that will be used when create new tables when
    default-storage-engine=INNODB
    
    # Set the SQL mode to strict
    sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
    
    # The maximum amount of concurrent sessions the MySQL server will
    # allow. One of these connections will be reserved for a user with
    # SUPER privileges to allow the administrator to login even if the
    # connection limit has been reached.
    max_connections=100
    
    # Query cache is used to cache SELECT results and later return them
    # without actual executing the same query once again. Having the query
    # cache enabled may result in significant speed improvements, if your
    # have a lot of identical queries and rarely changing tables. See the
    # "Qcache_lowmem_prunes" status variable to check if the current value
    # is high enough for your load.
    # Note: In case your tables change very often or if your queries are
    # textually different every time, the query cache may result in a
    # slowdown instead of a performance improvement.
    query_cache_size=0
    
    # The number of open tables for all threads. Increasing this value
    # increases the number of file descriptors that mysqld requires.
    # Therefore you have to make sure to set the amount of open files
    # allowed to at least 4096 in the variable "open-files-limit" in
    # section [mysqld_safe]
    table_cache=256
    
    # Maximum size for internal (in-memory) temporary tables. If a table
    # grows larger than this value, it is automatically converted to disk
    # based table This limitation is for a single table. There can be many
    # of them.
    tmp_table_size=103M
    
    
    # How many threads we should keep in a cache for reuse. When a client
    # disconnects, the client's threads are put in the cache if there aren't
    # more than thread_cache_size threads from before.  This greatly reduces
    # the amount of thread creations needed if you have a lot of new
    # connections. (Normally this doesn't give a notable performance
    # improvement if you have a good thread implementation.)
    thread_cache_size=8
    
    #*** MyISAM Specific options
    
    # The maximum size of the temporary file MySQL is allowed to use while
    # recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
    # If the file-size would be bigger than this, the index will be created
    # through the key cache (which is slower).
    myisam_max_sort_file_size=100G
    
    # If the temporary file used for fast index creation would be bigger
    # than using the key cache by the amount specified here, then prefer the
    # key cache method.  This is mainly used to force long character keys in
    # large tables to use the slower key cache method to create the index.
    myisam_max_extra_sort_file_size=100G
    
    # If the temporary file used for fast index creation would be bigger
    # than using the key cache by the amount specified here, then prefer the
    # key cache method.  This is mainly used to force long character keys in
    # large tables to use the slower key cache method to create the index.
    myisam_sort_buffer_size=205M
    
    # Size of the Key Buffer, used to cache index blocks for MyISAM tables.
    # Do not set it larger than 30% of your available memory, as some memory
    # is also required by the OS to cache rows. Even if you're not using
    # MyISAM tables, you should still set it to 8-64M as it will also be
    # used for internal temporary disk tables.
    key_buffer_size=175M
    
    # Size of the buffer used for doing full table scans of MyISAM tables.
    # Allocated per thread, if a full scan is needed.
    read_buffer_size=64K
    read_rnd_buffer_size=256K
    
    # This buffer is allocated when MySQL needs to rebuild the index in
    # REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE
    # into an empty table. It is allocated per thread so be careful with
    # large settings.
    sort_buffer_size=256K
    
    
    #*** INNODB Specific options ***
    
    
    # Use this option if you have a MySQL server with InnoDB support enabled
    # but you do not plan to use it. This will save memory and disk space
    # and speed up some things.
    #skip-innodb
    
    # Additional memory pool that is used by InnoDB to store metadata
    # information.  If InnoDB requires more memory for this purpose it will
    # start to allocate it from the OS.  As this is fast enough on most
    # recent operating systems, you normally do not need to change this
    # value. SHOW INNODB STATUS will display the current amount used.
    innodb_additional_mem_pool_size=7M
    
    # If set to 1, InnoDB will flush (fsync) the transaction logs to the
    # disk at each commit, which offers full ACID behavior. If you are
    # willing to compromise this safety, and you are running small
    # transactions, you may set this to 0 or 2 to reduce disk I/O to the
    # logs. Value 0 means that the log is only written to the log file and
    # the log file flushed to disk approximately once per second. Value 2
    # means the log is written to the log file at each commit, but the log
    # file is only flushed to disk approximately once per second.
    innodb_flush_log_at_trx_commit=1
    
    # The size of the buffer InnoDB uses for buffering log data. As soon as
    # it is full, InnoDB will have to flush it to disk. As it is flushed
    # once per second anyway, it does not make sense to have it very large
    # (even with long transactions).
    innodb_log_buffer_size=3497K
    
    # InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
    # row data. The bigger you set this the less disk I/O is needed to
    # access data in tables. On a dedicated database server you may set this
    # parameter up to 80% of the machine physical memory size. Do not set it
    # too large, though, because competition of the physical memory may
    # cause paging in the operating system.  Note that on 32bit systems you
    # might be limited to 2-3.5G of user level memory per process, so do not
    # set it too high.
    innodb_buffer_pool_size=339M
    
    # Size of each log file in a log group. You should set the combined size
    # of log files to about 25%-100% of your buffer pool size to avoid
    # unneeded buffer pool flush activity on log file overwrite. However,
    # note that a larger logfile size will increase the time needed for the
    # recovery process.
    innodb_log_file_size=50M
    
    # Number of threads allowed inside the InnoDB kernel. The optimal value
    # depends highly on the application, hardware as well as the OS
    # scheduler properties. A too high value may lead to thread thrashing.
    innodb_thread_concurrency=8
    estive agora a procura do que diz no texto do erro e nao encontro em nenhum .ini...

    será que o problema esta em eu não ter nesta pasta C:\Program Files\MySQL\MySQL Server 5.0\data\(meu login) os files mos_comment e mos_poll_data? é que aparecem nesta pasta muitos files começados por mos_... só que nenhum com este nome.

    há maneira de criar estes files e meter lá? como e com que extensão?

    abraço
     
    Última edição pelo moderador: 22 de Janeiro de 2008
  10. slack_guy

    slack_guy Power Member

    Como calculas, o ficheiro 'my.ini' não tem instruções SQL. É um ficheiro de configuração do servidor MySQL. Tens de procurar qual é o ficheiro que tem as instruções SQL que referiste.
     
  11. jnightz

    jnightz Power Member


    Acho que o problema talvez seja o NOT NULL default '', diz que NÃO é nulo e o valor default é nulo :).Se isso diz que não pode ter um valor default então tira o que lá estiver.
     

Partilhar esta Página