Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 0.8.6

Request #11961 Custom Field Type
Submitted: 2007-09-02 03:30 UTC
From: ifeghali Assigned: ifeghali
Status: Assigned Package: MDB2_Schema (version CVS)
PHP Version: Irrelevant OS:
Roadmaps: (Not assigned)    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 21 + 7 = ?

 
 [2007-09-02 03:30 UTC] ifeghali (Igor Feghali)
Description: ------------ I would love to have the ability to add annotations, so that if a database is created in a particular DBMS, you can specify exactly what kind of field to create. for instance, the kind of TEXT or INT field that is created. In the <field> tag, you could have: <customtype> <mysql>BIGINT</mysql> </customtype> this would allow advanced users to customize exactly how the field is created on different DBMS. beginners or people who don't care could use the guesswork, which is good enough for that level. the reverse engineering script would just spit out the tags for the current DBMS and version. this would allow us to customize for mysql 4.0/4.1/5.0 and so on. the goal is not to support everything - it would only spit out what the current dbms is, and the user can customize it if needed for other dbms * Feature requested by Greg *

Comments

 [2007-09-03 05:41 UTC] fornax (Andrew Hill)
I think you are looking for something like this? http://www.fornax.net/blog/archives/96-Custom-Types-in-PEARMDB2.html HTH,
 [2007-09-03 13:30 UTC] ifeghali (Igor Feghali)
Hi Andrew, Yeh it would be something in that direction, but this process have to be transparent and automatic to the user with the touch of a button ;) So rather than specifying every possible database native type for each DBMS version, we should skip the MDB2 datatype conversion and dumps to XML the exactly datatype that was specified by the PHP database diver.
 [2007-09-03 14:22 UTC] fornax (Andrew Hill)
Hi Igor, Ah, gotcha! A mode to enable exact type matching at the expense of portability. Seems like a resonable enough requirement for some applications :-) Cheers, Andrew