No data is saved

[kailew]

Hi,

- debug is set
- v.4.2
- no message

my problem is, that all things ae working quiet fine besides that there is saved no data. If I try to make a new entry with DaDaBIK then the entry is done but the're only a few Zero inside. Any ideas?

Kai



Post Edited (03-26-09 23:02)

 

[billthecat]

What's the data type of your database field, compared to the type of DaDaBIK?

 

[kailew]

Hi,

mmhhh ... I've different types of fields... I'm using an existing table with some fields. I can show them with DaDaBIK but not change etc. If I change an existing entry, the fields are empty after it. In some fields are some zeros ...

thats all.

whar do you mean with

"... compared to the type of DaDaBIK?"

Kai



Post Edited (03-27-09 00:28)

 

[billthecat]

Well for instance I've had trouble where a date field in DaDaBIK won't update a DATETIME field MySql.

I would check the Interface configurator to make sure the fields all match.

 

[kailew]

Hi billthecat,

he're my fields (first is mysql-type and after -> is DaDaBIK):

- Field 1(primary key): int(11)/auto_increment -> unique_id/numeric
- Field 2: varchar(64) -> text/alphanumeric
- Field 3: varchar(64) -> text/alphanumeric
- Field 4: smallint(2) -> text/numeric
- Field 5: smallint(2) -> text/numeric
- Field 6: mediumint(4) -> text/numeric
- Field 7: varchar(255) -> text/alphanumeric
- Field 8: smallint(3) -> text/numeric
- Field 9: smallint(2) -> text/numeric
- Field 10: smallint(2) -> text/numeric
- Field 11: mediumint(4) -> text/numeric
- Field 12: varchar(255) -> select_single/alphanumeric
- Field 13: varchar(255) -> select_single/alphanumeric
- Field 14: datetime -> insert_date/numeric
- Field 15: timestamp/current_timestamp -> update_date/numeric

is there a mistake?

Kai

 

[DebbieS]

I've normally left my date/timestamp fields a alphanumeric in DaDaBIK interface configurator. Also, leave your primary key as text/alphanumeric and see if that makes a difference.

 

[kailew]

Hi DebbieS,

as far as I can see .... no difference ...

Kai

 

[billthecat]

Try it by changing:

- Field 14: date -> insert_date/numeric
- Field 15: date -> update_date/numeric

According to the documentation, insert_date and update_date must both be set as date types.

 

[kailew]

sorry ... bur again no result ...

If I try to save a new entry, I only get "0" in the numeric fields and the other fields are empty.

And: I'm using "utf8_general_ci" in the alphanumeric fields. Could this cause problems?

Kai



Post Edited (03-28-09 07:50)

 

[billthecat]

I doubt that the collation would do anything....how about the field names? Are there any fields with spaces or dots?
IE `field name` or `field.name`

 

[kailew]

Hi billthecat,

here's a list with the field names:

TodID
Name
Vorname
Tag
Monat
Jahr
Beruf
Alter
Geburtstag
Geburtsmonat
Geburtsjahr
Land
Weblink
Erstellt
Bearbeitet

I don't think that the're is the problem ...

Kai

 

[DebbieS]

Have you tried with your primary key field (TodID) set to text/alphanumeric in DaDaBIK? Others have reported trouble using unique_id with auto-increment.

Also, try renaming the field "Name" to something else (just make it read "Name" for display through the admin interface config). I've seen things cack on reserved words before (maybe "name" is reserved on your server?).

Is this located somewhere it can be viewed?