Octavian Rasnita wrote:
This approach *is* best practice and it *does* work fine for
SQLite, MySQL and Postgres at least.
So far I can confirm this at least for MySQL.
I had a short look on PostgreSQL and noticed that there is no support
for ENUMs, neither directly (AFAIK ENUM is quite new
From: Bernhard Graf [EMAIL PROTECTED]
mydate date(10)
Simply don't specify the size for date/datetime/tim fields.
Can be counted as a bug at least for MySQL and SQLite (Pg seems OK).
and the enum() field doesn't remember the field elements.
The field elements for enum field types are not
From: Bernhard Graf [EMAIL PROTECTED]
Octavian Rasnita wrote:
Aha, so actually you are saying that the DBIC::Schema Catalyst helper
doesn't create a complete and valid schema, and I must edit it
manually.
That's my way ATM:
1. Data definition for MySQL in plain ASCII (because I'm used to
On Sat, 15 Nov 2008 07:24:54 +1100, Michael Higgins [EMAIL PROTECTED] wrote:
Nov 14 12:01:54 lappy perl: pam_unix(system-auth:auth): check pass; user
unknown
Nov 14 12:01:54 lappy perl: pam_unix(system-auth:auth): authentication
failure; logname=mykhyggz uid=0 euid=0 tty= ruser= rhost=
Matt S Trout wrote:
On Tue, Nov 04, 2008 at 05:56:51PM +1100, Adam Clarke wrote:
Our first experiences of trying to use
it were quite frustrating - there were zillions of dependencies to be
met and this could take a fair bit of perseverance since they would
often fail to install for
