Re: Frontbase [Solved]
Re: Frontbase [Solved]
- Subject: Re: Frontbase [Solved]
- From: Chuck Hill <email@hidden>
- Date: Mon, 2 Oct 2006 15:49:59 -0700
On Oct 2, 2006, at 12:48 PM, David Holt wrote:
I looked at the SQL generated by my application and there is a
derived value in my table that uses a coalesce function that refers
to a field in another table (to-one relationship). On the fetch, it
was selecting the derived field as well.
As the relationship itself was optional, I didn't think to generate
null values in that table when I created records in the original
table. As soon as I created null entries on the secondary table,
everything works as expected. Looks like my derived field was
causing the problem in both EOModeler and my app.
Another option, and one that I have not tried, is to change the join
type for this relationship from inner to a left outer join.
Chuck
On 2 Oct 2006, at 12:21 PM, David Holt wrote:
Hmmmm. The data browser in EOModeler isn't showing the inserted
records either. I'll take a closer look at the data as you
suggest. Thanks,
David
On 2 Oct 2006, at 12:18 PM, Chuck Hill wrote:
I would then guess that the flat file import may have appended
spaces to the String/Varchar values. Dates may have also gone in
differently than they do from the app.
Check the SQL that your app is generating. Try it in FrontBase
Manager. See which part of the WHERE clause is failing to
match. After that it sounds like you will have some data
cleanup to do.
Regards,
Chuck
On Oct 2, 2006, at 12:13 PM, David Holt wrote:
Hi Chuck,
On 2 Oct 2006, at 12:05 PM, Chuck Hill wrote:
On Oct 2, 2006, at 11:55 AM, David Holt wrote:
Frontbase generates Primary Keys starting at 1000000. I have
just imported a bunch of records with PKs below that range
using Frontbase manager.
What exactly did you do here? I don't see any Import function
in FB manager. Do you mean that you created a new database
from the result of a WRITE ALL?
If you connect to the database there is a flat file importer
under File>Import...
The database already exists and contains several records
starting in the 1000000 range.
I imported a .csv file using the text file import. The primary
keys of the records are from 20000 to 20130. There are several
records that I have inserted through the WO application
interface. Any additional records that I upload show up in the
app and in Frontbase manager.
My WO app will not fetch these additional records, and I can't
figure out why. Is there a mechanism behind the scenes that I
have to reset?
The fetching should have nothing to do with the PK.
This was my assumption!!
You can easily edit the DDL from EOModeler to start PK
generation at 1 instead of 1000000. The only other thing I can
think of is that the import did not update the indexes.
I tried dropping and recreating the index. It didn't have any
effect.
Chuck
--
Practical WebObjects - for developers who want to increase
their overall knowledge of WebObjects or who are trying to
solve specific problems. http://www.global-village.net/
products/practical_webobjects
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve
specific problems. http://www.global-village.net/products/
practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems. http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden