Re: PostgreSQL plugin
Re: PostgreSQL plugin
- Subject: Re: PostgreSQL plugin
- From: 時期 精霊 <email@hidden>
- Date: Wed, 15 Jun 2005 10:53:06 +0200
Hello,
because Wonder use eclipse and the source tree is not clean.
Regards
Kuon
On Jun 14, 2005, at 10:44 PM, Hunter Hillegas wrote:
Why not integrate your changes into the Wonder source tree to avoid
forking this plugin?
On Jun 14, 2005, at 12:31 PM, 時期 精霊 wrote:
Hello,
I'm maintaining updated source of postgresql plugin.
It is based on the project wonder plugin, but actively maintained
and has been updated to add many bugs fix.
We plan to post the source on our new website. But we are actually
under heavy reorganization.
If you want, I can unofficially send the source to you, I'll just
ask you to tell us of any bug fix we can add to our repository.
Regards
Kuon
On Jun 14, 2005, at 7:34 PM, Leo Lutz wrote:
Thanks, that was the problem. Somehow didn't see the bpchar since
there were a lot of varchar already on other fields. Is this a
problem
we can get fixed in the plugin or is it completely up to EOModeler?
BTW, I would still like the updated plugin source if anyone has it.
--Leo
On 6/13/05, Omar <email@hidden> wrote:
I had this same problem this weekend, what I did was change the
"bpchar"
in my model to varchar, I think just "char" should work though...
Omar
Leo Lutz wrote:
I've tried the modified files I found posted on this list and they
seem to work great except I still can't run a simple query.
I'm getting this as the query and error.
SELECT t0.correcting, t0.formid, t0.moddate, t0.status FROM
public.status t0 WHERE UPPER(t0.status) LIKE UPPER($1::bpchar(1))
ESCAPE '|'
ERROR: 42601: syntax error at or near "(" at character 122
122 starts at (1)) in bpchar(1))
I've asked about this and it seems that the plugin should be
putting
in a char(1) instead of a bpchar(1) because the parser doesn't
know
how to handle (n) for bpchar.
Is it possible to get the source for the plugin or is there
some other
reason for this problem?
--Leo
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40carvajalc.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40goyman.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40mac.com
This email sent to email@hidden
_______________________________________________
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