Defaults not set on fresh install Windows...

[rkah]

Should the script that generates the oscMax db be updated on windows side to include the defaults for customer_payment_allowed, and customer_shipping_allowed. (set default values for those fields in the oscmax db create sql script). Im not totally familiar with the insides of this store yet, so Im wondering how that information should come over. I would think that as a customer creating their own account, they would be retail, and that value should cascade down from the group. But this is not happening. Im just thinking of others who try to set this up (atleast from a windows perspective, cause maybe there are differences in the code base). I had a heck of a time getting to the conclusion and for those who are not at all database savvy they would never find the answers I did.


The gender is also not included on the main account creation page, so should the value for gender be set to true initially in the admin page under customer details? Because it is set to a be a required field in the customer table.

One last question before I go. How do I set the store to default to use authorize.net? I know how to set it in the db, but is there not a place in the admin tool for this?

[gordnm]

Just thought this might help you.
This excerpt was from MySql's website (http://dev.mysql.com/doc/refman/5.0/ ).

As of MySQL 5.0.2, if a column definition includes no explicit DEFAULT value, MySQL determines the default value as follows:
If the column can take NULL as a value, the column is defined with an explicit DEFAULT NULL clause. This is the same as before 5.0.2.
If the column cannot take NULL as the value, MySQL defines the column with no explicit DEFAULT clause. For data entry, if an INSERT or REPLACE statement includes no value for the column, MySQL handles the column according to the SQL mode in effect at the time:

• If strict SQL mode is not enabled, MySQL sets the column to the implicit default value for the column data type.
• If strict mode is enabled, an error occurs for transactional tables and the statement is rolled back. For non-transactional tables, an error occurs, but if this happens for the second or subsequent row of a multiple-row statement, the preceding rows will have been inserted.

So turn off strickt SQL mode.

Hope this helps.

gordnm