I committed a fix for invalid characters, but it doesn't test for
duplicates, so the problem is only half solved.
2008/10/30 Eugene Kotlyarov <[EMAIL PROTECTED]>
>
> for example change in create_Northwind_ora.sql
> CREATE TABLE "Region" (
> "RegionID#" INTEGER NOT NULL,
> "RegionDescription" VARCHAR(50) NOT NULL,
> PRIMARY KEY("RegionID#")
> );
>
> RegionID# is valid field name in Oracle, but it is invalid identifier
> in C#
> On 30 окт, 22:45, Jiri Moudry <[EMAIL PROTECTED]> wrote:
> > ekot, I experimented and found that for variable names, some special
> > characters are allowed in Oracle queries, eg.
> > SELECT e$.Name FROM Employees e$
> >
> > You mention field names - can you give us an example?
> > Thanks,
> > Jiri
> >
> > On Oct 29, 12:47 pm, "Pascal Craponne" <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > > SqlMetal replaces invalid characters by underscores ("_"), so maybe
> DbMetal
> > > should do the same.If you have a patch, please post it here, we'll
> commit
> > > it.
> >
> > > On Wed, Oct 29, 2008 at 19:45, ekot <[EMAIL PROTECTED]> wrote:
> >
> > > > Hi
> >
> > > > I'm trying to test dblinq with Oracle, and there is a problem when
> > > > field name contains special characters like '#' or '$'. Such field
> > > > names are valid in Oracle but invalid in C#.
> >
> > > > For now I just made patch to skip them but I wonder what is the right
> > > > way to deal with them?
> >
> > > --
> > > Pascal.
> >
> > > jabber/gtalk: [EMAIL PROTECTED]
> > > msn: [EMAIL PROTECTED]
> >
>
--
Pascal.
jabber/gtalk: [EMAIL PROTECTED]
msn: [EMAIL PROTECTED]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"DbLinq" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/dblinq?hl=en
-~----------~----~----~----~------~----~------~--~---
