Hi, I'm working through fixing up a bit of SSL code and have encountered
a difficulty. The PHP manual[1] says that unused parameters "may be
given as NULL". In my testing, setting them = ''; works fine, but of
course we want to do what PHP expects. In config.inc.php, we don't have
any values that default to NULL, and I think it may confuse users in
this case. I'd much prefer to leave them set = ''; in config.inc.php for
consistency and to make it easy for users to plug in their own values.
What I am thinking of is in libraries/config.default.php to set the
parameters to NULL, then if the user decides to overwrite it in
config.inc.php there is no problem. In that case, I'm not sure I'd write
the end-user documentation as if the default was = ''; or NULL.
If my question has made sense, what do you think?
1 - http://php.net/manual/en/mysqli.ssl-set.php
I was writing Selenium tests for creating a table. In the interface, I tried to add a column, named "id", set it to type "int" and selected Index as "Primary", and clicked the A_I checkbox. It gave me an error "Multiple primary key defined"
I had an older version (3.4.2), I tried this there, and it allowed me to create the table. Is this a known bug in the latest release?
--
Ayush Chaudhary
I wrote down the following, but don't recall details:
"Query analyzer from status zoom is broken" -- anyone remember further
information about this problem?
While studying the current Selenium test cases, I came across a design/organisation issue. This issue is related to redundant actions. For example, if we want to test the creation of a table, we need to create a database. We create a database already in the 'create database' test. Similarly, if go deeper into the flow, to test insertion of records in a table, we need to create a table which in turns needs us to create a database. If we have separate tests for these - (namely, 'Create a table', 'Insert a Record') we will be doing some actions redundantly, that is creating a database and creating a table and so on. Apart from the problem of redundancy, the tests will take a longer time to execute unnecessarily.
The alternatives that we might go for are:
1. Create one single test that tests everything in the flow - creating a db -> creating a table -> inserting records, searching, editing (and other tasks) -> drop table -> drop db. The downside is that this will create a very long test in terms of length.
2. Enforce the pre-requisite of having a testdb and some tables in that test db specifically for Selenium test cases wherever Selenium tests are supposed to be run. The downside is that this will create an extra and perhaps unnecessary dependency on the environment.
Looking for some inputs on which approach might be better.
Thanks!
--
Ayush Chaudhary
Hi,
A user is in IRC with some trouble doing an export from phpMyAdmin and
import to another machine. The machine he's importing to
#1064 - You have an error in your SQL syntax; check the manual that
corresponds to your MySQL server version for the right syntax to use
near ''pageclass_sfx=\nback_button=\nitem_title' at line 52
The slightly obscured relevant section of the SQL file reads
INSERT INTO `jos_contact_details` (`id`, `name`, `con_position`,
`address`, `suburb`, `state`, `country`, `postcode`, `telephone`, `fax`,
`misc`, `image`, `imagepos`, `email_to`, `default_con`, `published`,
`checked_out`, `checked_out_time`, `ordering`, `params`, `user_id`,
`catid`, `access`) VALUES
(1, 'Joe', '', 'foo', 'Arima', 'State', 'bar', '', 'baz', '(868) 642
3164', 'Miscellanous info', '', 'top', 'foo', 0, 0, 0, '0000-00-00
00:00:00', 10,
'menu_image=-1\npageclass_sfx=\nprint=\nback_button=\nname=2\nposition=1\nemail=0\nstreet_address=1\nsuburb=1\nstate=1\ncountry=1\npostcode=1\ntelephone=1\nfax=1\nmisc=1\nimage=1\nvcard=0\nemail_description=1\nemail_description_text=\nemail_form=1\nemail_copy=0\ndrop_down=0\ncontact_icons=0\nicon_address=\nicon_email=\nicon_telephone=\nicon_fax=\nicon_misc=',
62, 12, 0)
Nothing looks odd there, and indeed it works properly for me to import
on the demo server. He's using MySQL 5 and phpMyAdmin 4.1 for the
import. Any thoughts about why he's having trouble? I don't see any
obviously incompatible statements.